Workflows — Delinked Nodes (Independent Branches)

Delinked Nodes let you build independent branches (mini-flows) on the canvas that aren’t wired into a single main line. Use them to design parallel paths side-by-side and start each branch from the trigger you choose.

Overview

• Build in multiple clusters: Place actions anywhere to create independent clusters (no need to chain everything together).

• Route explicitly: Start any cluster by pointing a trigger to it using Trigger Go-To (dashed connector).

• Stay readable: Separate branches are easier to scan, document, and evolve over time.

What are Delinked Nodes?

Delinked nodes are actions laid out as independent clusters that don’t have to connect to your “main” chain.
They do not run on their own—you must route a trigger (or another node) to the first action in the cluster.

Key behaviors & visuals

• Independent clusters: You can position and format clusters anywhere on the canvas.

• Trigger with go-to connection required: Use the dashed Go-To connector from a trigger to the cluster’s first action to make it executable.

• Execution: Each routed branch runs independently in the same workflow context.

Set up Delinked Nodes (step-by-step)

1. Open Advanced Builder and lay out your actions as one or more delinked clusters.

2. Choose a trigger on the canvas.

3. Drag the dashed Go-To connector from the trigger to the first action of the delinked cluster you want to start.

4. (Optional) Add sticky notes and colors to label branches for teammates.

5. Save → Publish to make the behavior live.

Examples

• Separate onboarding tracks: New form submissions start at a “Welcome” cluster; VIP tag added starts directly at a “High-Touch” cluster.

Best practices

• Name clusters with sticky notes: e.g., “VIP Onboarding,” “Ops Sync,” “Trial Nurture.”

• Keep first actions obvious: Place the intended entry node at the top/left of each cluster.

• Minimize crossings: Use Tidy/Format and spacing so dashed Go-To lines are easy to read.

Additional Points

• Advanced Builder only - The delinked nodes are available only in the advanced builder.

• Single enrollment per contact: A contact will not run through multiple branches concurrently in the same workflow.

• Explicit routing: A delinked cluster won’t execute unless at least one trigger is connected to it.

• Switching back to Standard Builder: Remove Delinked Nodes (and other Advanced-only features like Trigger Go-To or Disabled nodes) before switching.