Skip to main content
Picks one of several named branches based on a value computed by an inner graph. Drill in to edit the inner graph — it runs once per evaluation and should emit a string. That string is matched against the Name of the Flow Branch nodes attached to this switch. Exactly one branch is entered per run; the rest are pruned (sharing nodes between branches is fine — only nodes reachable only from losing branches are skipped). If the inner graph emits nil, a non-string, or a name with no matching branch, the flow halts with an error — there’s no implicit default. Add an explicit "default" branch yourself if you want one.

​
Configuration

  • Decide by — Rule: a one-line text rule yields the branch name (if salary_amount > 40000 then "high" else "standard"; true/false pick branches named so). Inner engine: the graph below does.
  • Rule — the text rule, when deciding by rule. Names resolve to the subject’s attributes first, then to flow assigns (employee.salary_amount). See Expressions for the full language.
  • Subject assign (optional) — assigns key whose value becomes the subject for Attribute nodes inside the inner graph, or for bare names in the rule. Typical pattern: point at the employee / schedule you’re branching on so you can read its dated properties directly.

​
Example

Branch on an employee’s position: inner graph reads position_name via an Attribute node, ends on that value. Attach Flow Branch nodes named "Manager", "Engineer", "default" (one for any catch-all).

​
Ports