Build Independent Branches with Delinked Nodes
Delinked nodes let you place clusters of actions anywhere on the Advanced builder canvas without chaining them into a single main line. Each cluster is its own mini-flow that you start by pointing a trigger at it.
How they behave
- A cluster does nothing on its own. It only runs when a trigger (or another step) is routed to its first action.
- You route using a dashed Go-To connector drawn from a trigger to that first action.
- Each routed branch runs independently within the same workflow context.
- A contact does not move through several branches at the same time inside one workflow.
Set one up
- Switch the workflow to the Advanced builder.
- Place the actions of your new branch on an open area of the canvas.
- Select the trigger that should start the branch.
- Drag the dashed Go-To connector from that trigger to the branch's first action.
- Optionally label the cluster with a colored sticky note, such as "VIP Onboarding."
- Save and Publish.
Why use them
- Several related paths sit side by side instead of in one long column.
- You can test one branch without disturbing the others.
- Related automations stay in one workflow rather than being split across many.
Cautions
- Delinked nodes exist only in the Advanced builder. Remove them, along with other Advanced-only elements, before switching back to Standard.
- A cluster with no trigger connected to it will never run.
Good to know: Put each cluster's entry action at its top-left so anyone reading the canvas can find where the branch begins.
Was this article helpful?
