Conditional Branch
Last Updated: October 25, 2026
The Conditional Branch step lets you define branches to route a workflow to different steps based on data from any previous workflow source. Each branch represents a different path the workflow takes when a specified condition is met.
Key Points
A Conditional Branch step includes a default branch, which executes when no custom branch conditions are met, and one or more custom branches. Review the following key points:
- You can add up to five custom branches per Conditional Branch step.
- Each branch evaluates a condition using four fields: Sources, Variables, Conditions, and Value.
- You configure branches in a side panel that opens automatically when you place the step on the canvas. Changes save automatically.
- After you configure the step, you connect each branch's output point to a later step on the canvas.
How Conditional Branch Works
When a workflow reaches a Conditional Branch step, the step evaluates each branch's condition in order. If a branch's condition is met, the workflow routes to the step connected to that branch. If no custom branch condition is met, the workflow routes to the step connected to the default branch.
You define each branch condition by selecting the following:
- Source: The previous workflow step that provides the data, for example, a form, a document event trigger, an Intelligent Document Processing step, or an Agent step.
- Variable: The specific field or data point from that source, for example, "Invoice Amount" or "File Type." For an Agent step, the variable is agentResult.
- Condition: The comparison operator appropriate for the variable's data type, for example, "Greater than" for numeric variables or "Contains" for text variables. For the agent result, use a text condition, such as "Starts with" or "Contains."
- Value: The value to compare against, for example, "5000" or "Invoice."
To route a workflow based on an agent response, tell the agent to return a specific value, such as "Approved" or "Denied". Refer to Agent Step Prompts.
Requirements
Review these Requirements before you start.
In addition to the general requirements, a Conditional Branch step requires the following:
- The workflow must include at least one previous step that emits variables before the Conditional Branch step.
Next Steps
Refer to the following:
In this topic: