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

# Can workflows branch based on outcomes?

> Route workflow steps using the outcome branches supported by each action node.

Yes. In **Outbound → Workflows**, action nodes can expose outcome-based connections. The available branch depends on the source node.

Common branch labels include:

* Text or email: **If replied** and **If no reply**
* Call: **If answered** and **If unanswered**
* Human callback: **If completed** and **If not completed**
* Direct mail: supported printing, sent, or delivery milestones

Connections can also include a delay. Trigger and some channel-specific nodes use an immediate or delayed connection without an answered/unanswered branch.

## Build a branch

1. Open [the Avoca dashboard](https://dashboard.avoca.ai) and go to **Outbound → Workflows**.
2. Open or create a workflow.
3. Connect the action node to the next step for each supported outcome.
4. Select the outcome and set the delay on each connection.
5. Provide a reasonable path for every outcome the node can produce.
6. Resolve validation errors and save.
7. Test the workflow with a limited campaign audience.

<Note>
  A replied/no-reply branch does not automatically mean the workflow understands arbitrary keywords or customer intent. Use only the outcomes and configuration shown in the editor.
</Note>

After launch, check campaign results and conversation history to confirm contacts followed the expected paths.