Delinked Nodes in Sparkforge Advanced Workflow Builder

Delinked Nodes are actions laid out as independent clusters that don't have to connect into a single main chain. They do not run on their own — a trigger (or another node) must route into the cluster's first action via the Go-To connector.

What you can do with them

• Build in multiple clusters: place actions anywhere on the canvas without chaining everything together.
• Route explicitly: start any cluster by pointing a trigger to it with a dashed Go-To connector.
• Stay readable: separate branches are easier to scan, document, and evolve.

Why use them

• Visual clarity: side-by-side branches beat long vertical chains.
• Faster testing: isolate and debug one branch without touching others.
• Single source of truth: keep related automations together rather than spawning separate workflows.
• Flexible scaling: add or remove clusters without redrawing the main flow.
• Pairs with Advanced features: works alongside Go-To connections, sticky notes, and color-coding.

Set up a delinked cluster

1. Choose a trigger on the canvas.
2. Drag a dashed Go-To connector from the trigger to the first action of the cluster.
3. Add sticky notes and colors to label the branch (optional).
4. Save and publish to make the branch live.

Best practices

• Name clusters with sticky notes (e.g. "VIP Onboarding," "Ops Sync," "Trial Nurture").
• Place each cluster's entry node at the top or left so the start is obvious.
• Use Tidy/Format and spacing so dashed Go-To lines stay readable.

Important takeaways

• Advanced Builder only: delinked nodes are not available in the Standard Builder.
• Single enrollment per contact: a contact runs through only one branch 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) first.