Branch
Step · Stable
Conditional yes/no routing — evaluate a condition and follow one arm.
Exclusive routing. The condition (a Jinja boolean expression) evaluates to true or false; exactly ONE of the two labelled out-edges is followed. The arms are mutually exclusive — both will never run in the same execution. Convention: green = YES / true, amber = NO / false. Edge labels are case-insensitive (yes/true vs no/false). Reconnect the arms downstream with a Merge node.
When to use
Section titled “When to use”Use for a single binary decision where the upstream output is a boolean or a simple comparison — e.g. “is invoice amount > 10 000?” or “did the actor approve?”. The YES arm and NO arm carry the full context so downstream steps can read any prior output.
When not to use
Section titled “When not to use”If you are routing on a value that has 3 or more distinct buckets (e.g. deal stage: won / lost / in-progress), use Switch — nesting two Branch nodes for that case is far less legible. Reconnect both arms afterwards with Merge.
Inputs
Section titled “Inputs”Configured per use: condition.
Auto-generated from the skill registry (load_skills()). Do not edit by hand.