Workflow Docs

Sub-nodes

Smaller branch steps on the board, attached to a parent step.

Sub-nodes are smaller nodes drawn beside a parent on the canvas. Each sub-node has its own outgoing handle so you can connect a different path per branch.

When to use

Sub-nodes appear automatically (or after you add them) when the parent needs multiple exits:

  • WhatsApp / Messenger / Instagram — button/quick-reply answers, plus optional fallback and timeout when waiting for a reply.
  • If / Else — fixed true and false evaluation branches.
  • Switch — one branch per case, plus an initial fallback when you add the first case.

Configuration (parent vs child)

LayerWhat you configureWhere
ParentEnable wait-for-response, buttons, switch cases, etc.Parent node form in the sidebar
Sub-nodeFallback message, timeout timer, case label, or (for switch cases) full If-style conditionsSelect the sub-node on the canvas, then use the sidebar form

Sub-nodes do not have a Description field. Use inline labels on the canvas or the parent node’s description for team notes.

Not every sub-node has a rich form. Answer sub-nodes are often edited inline on the canvas (label/badge). Switch case sub-nodes reuse the same condition UI as If / Else when selected.

Flow behavior

  • Sub-nodes belong to their parent; you connect the next step from each sub-node’s handle.
  • When sub-nodes exist, the parent’s main output handle is hidden; execution continues from the branch handles.
  • Downstream variable pickers still see trigger and message context from the parent path.
  • Limits apply per parent (for example, up to 10 answer sub-nodes on WhatsApp, 25 switch cases).

WhatsApp-style branches

When Wait for user response is on:

  1. Answer sub-nodes — one per button/quick reply; labels sync to the template when applicable.
  2. Fallback — runs when the user does not tap an expected button.
  3. Timeout — runs when no reply arrives within the configured time.

Switch-specific behavior

Adding the first case on a Switch creates a Fallback sub-node and clears direct edges from the switch parent. Further + clicks add Switch case sub-nodes; each case can be configured with If / Else rules in the sidebar.

Examples

  1. Configure WhatsApp with three quick-reply buttons.
  2. Three answer sub-nodes appear; connect each to a different next step.
  3. Configure Fallback for “invalid” input and Timeout for silence.

Route by variable with Switch

  1. Add Switch after a node that exposes a variable.
  2. Add cases with +; open each case sub-node and set conditions (same fields as If / Else).
  3. Wire each case handle to the appropriate action.

On this page