Workflow Docs

Switch

Route the flow across multiple labeled cases with optional fallback.

The Switch node sends execution down case branches. Each case is a Switch case sub-node on the canvas with its own outgoing handle. Cases reuse the same condition editor as If / Else when selected in the sidebar.

When to use

  • Multi-way routing (more than two paths) based on variables.
  • Menu-style options where each label maps to a branch.
  • Default path when no case matches (via Fallback sub-node).

Configuration

WhereFieldWhat it does
Parent (canvas)+ controlAdds cases (up to 25); first click adds Fallback
Case sub-node (canvas)Label badgeEdit/removable case name (max 20 chars); registers a string variable on parent
Case sub-node (sidebar)Same as If / ElseRule, conditions, comparisons, add/delete condition
Fallback sub-nodeFallback form / labelPath when no case matches (first sub-node created)

Switch uses the legacy node layout: Description in the sidebar is saved but not drawn on the Switch card. Sub-nodes have no Description field. See Node descriptions.

Adding cases

  1. Click + on the Switch node.
  2. First click: creates a Fallback sub-node and removes direct edges from the switch parent.
  3. Later clicks: add Switch case sub-nodes with editable labels (default names like Option #1).
  4. Each new case can expose a label for downstream variable pickers.

Case conditions

Select a case sub-node to open the same condition editor as If / Else in the sidebar:

  • Rule: ALL vs ANY across conditions in that case.
  • Condition rows: variable, comparison, value (identical operators to If / Else).

Reorder cases with up/down chevrons when multiple siblings exist.

Flow behavior

  • When case sub-nodes exist, connect the next step from each branch handle (not from the parent’s main handle).
  • Limits: Up to 25 case sub-nodes; you can edit labels on the canvas and remove cases when allowed.
  • Variable pickers on a case still list upstream fields from the main flow into the Switch.

Examples

Route by language variable

  1. Add Switch after a node that sets language.
  2. Add cases en, he, ar (edit labels on canvas).
  3. Open each case; set Equals on language variable.
  4. Configure Fallback for unknown languages.

Product line menu

  1. Add cases for sales, support, billing.
  2. Connect each case handle to a different Messenger or Task path.

On this page