Branch splits an automation into several labeled paths, each guarded by its own condition. When the run reaches a Branch, every condition is evaluated and all matching paths execute — potentially in parallel. Use Branch when an item can take more than two distinct routes, such as routing a support ticket by priority or handling "approved", "rejected", and "needs info" as separate outcome sequences.

Overview

The Branch node splits the automation into several labeled paths, each with its own condition. You set a condition per path, and when the run arrives the Branch evaluates every condition — paths whose conditions are true execute, others are skipped. Unlike the Condition node (one true path, else continue), Branch is designed for several distinct outcomes running side by side.

Branch supports between 2 and 11 paths; three are available by default, and you can add more using the plus icon.

Use Cases

A practical example involves bucketing Zendesk tickets by priority and routing notifications through Slack, Gmail, or Asana:

• Set a Branch node comparing ticket priority across different branches.

• In each branch, configure priority conditions with corresponding app actions.

• Optionally, add an explicit catch-all branch to handle tickets that match none of the priority conditions, so no item is silently skipped.

Branch node Use Cases — ticket routing across labeled priority paths

Additional Features

• No-match behavior — When no branch conditions are true, the run continues past the Branch to whatever comes next. No automatic default branch is added; add an explicit catch-all branch if you need to act on unmatched items.

• Branch Addition — Use the add button to accommodate additional condition sets (up to 11 total).

• Branch Deletion — All branches except the initial two can be removed.

• Branch Copying — Branches can be copied and pasted directly into other nodes.

• Branch Pasting — Two options available: "paste above" or "paste below" within the same branch.

Branch node Additional Features — add, delete, copy, and paste branch controls

Advanced Logic, Routing, and Execution Capabilities

The Workflow Engine supports:

• Switch-style conditional logic for multi-path decisions

• Deep decision trees for multi-level branching flows

• 40+ built-in logical operations (containment, pattern matching, boolean combinators)

• Parallel branch execution for improved processing speed

• Workflow merging functionality after parallel execution

• Synchronization points ensuring all branches complete before advancing

Branch node advanced parallel execution and merge behavior

Race condition warning: When multiple branch conditions are true, those branches run in parallel and proceed independently. Do not write to the same record or session variable from two branches that can both match at the same time — the result depends on timing. If you need branches to execute in a fixed order, design that ordering explicitly (for example, a single path with sequential conditions) rather than assuming it.

Debug mode behavior: In debug / step-through mode, the Branch executes matching paths sequentially instead of in parallel, so you can inspect each one individually. This is a testing convenience — in a live run, matching branches run in parallel. Do not rely on the debug order for correctness in production.

Notes

Keep the following in mind when building automations with the Branch node.

• Matching branches run in parallel at runtime — do not write to the same record or session variable from two branches that can simultaneously match.

• Debug / step-through mode runs matching branches sequentially; production runs them in parallel. What you observe while stepping is not what you get in a live run.

• When no branch conditions are true, the run continues past the Branch to the next node — it does not stop. Add a catch-all branch if you need explicit handling for unmatched items.

• Branch supports between 2 and 11 paths; plan your condition set before adding branches to keep the logic readable.

• Use Branch for three or more distinct outcome sequences. For a simple "only-if" gate with no alternative steps, the Condition node is the simpler choice.

Review your branch conditions whenever two or more paths could match the same item and any of those paths write to shared data or state.