> ## Documentation Index
> Fetch the complete documentation index at: https://learn.workflow.dog/llms.txt
> Use this file to discover all available pages before exploring further.

# Actions reference

> How WorkflowDog actions (nodes) work and how to use this reference.

# Actions reference

In WorkflowDog, **actions** are the steps in your workflow graph. Each action is a **node**: it can take inputs from the trigger, from other nodes, or from settings you configure on the node itself. Nodes pass **outputs** to downstream actions.

This site documents every built-in action, grouped by **package** (Text, Core, Gmail, and so on—the same groupings you see when adding actions in the editor).

## Finding an action in the editor

Open the action picker and search by name, or browse by package. Many nodes also define **keywords** so alternate terms (e.g. “boolean” for True/False) still find the right action.

## Types of inputs

* **Connections** — Values wired from another node’s output (or from the trigger).
* **Configuration** — Fields edited on the node (text areas, toggles, dropdowns). These often don’t appear as handles on the graph.
* **Lists / repeat fields** — Add multiple items (e.g. multiple query parameters or recipients).
* **Accounts** — Integrations that need a linked third-party account use an account picker or an **Third-Party Account** node wired into the action.

## Lists on the graph

Some inputs and outputs are **repeatable** (lists). You can connect a whole list or expand entries and wire individual items. Modes like **entire list** vs **per item** affect how data lines up between **Loop Workflow**, **Zip Lists**, and similar nodes—use the handles’ labels and the editor tooltips when in doubt.

## Outputs and optional data

If an output has no value (for example, something was not found), downstream behavior follows the product rules for empty or missing data—some branches may not run. Prefer explicit handling (e.g. **Fallback**, **Is Null?**) when the workflow must react to missing data.

## Callable workflows and sub-workflows

Several actions run another workflow you select (**Run Workflow**, **Loop Workflow**, **Filter With Workflow**, **Find With Workflow**, **Transform Properties**, etc.). The target workflow usually must be **callable**. Use **Callable Workflow** to pass a workflow as data, and **Return Data** (where supported) to send a result back to the caller.

## Where to read next

* **[All packages](/reference/nodes)** — Index of every package and link to full node lists.
* **Package pages** — Under **Nodes by package** in the sidebar; each page lists every action in that package with its description and important behavior notes.