Go-To Connections for Triggers in Sparkforge Workflows

By Sparkforge Support Team ·Last reviewed May 3, 2026

Go-To Connections for Triggers let you set a unique start action for every trigger in a single workflow using a dashed connector — no duplicate workflows, no giant if/else stacks.

Go-To Connections for Triggers are dashed connectors that pick a unique first action for every trigger on the Advanced Builder canvas. When a trigger fires, the contact jumps directly to that connected action and the workflow continues from there.

How they work

  • Set a start action per trigger: drag a dashed Go-To from the trigger to the action where the path should begin.
  • Visual routing: trigger Go-To links are dashed with an arrowhead; sequential paths stay solid.
  • Direct execution: contacts skip everything between the trigger and the start action.

Why use them

  • One trigger, one journey — design multiple entry paths inside one workflow.
  • Cleaner logic — cut giant if/else branches.
  • Faster execution — contacts start exactly where they should.
  • Easy maintenance — drag a new dashed line to repoint a trigger in seconds.

Connection rules

  • 1:1 connections only: each trigger connects to one next action; each action accepts one incoming connection.
  • No branching from a single action: an action can have only one Next step. A new connection overwrites the existing link.

Enrollment rules

  • One trigger per enrollment — a contact enters the workflow once per run, attributed to the single trigger that fired.
  • If multiple triggers qualify around the same time, the workflow records one enrollment for that moment.
  • If re-entry is allowed, the same contact may enter again later when another trigger fires — each run still ties to one trigger.

Important notes

  • Advanced Builder only: Go-To Connections for Triggers are exclusive to Advanced Builder.
  • Every trigger must connect once: unassigned triggers auto-connect to Root, but set the correct start action explicitly.
  • Single enrollment per contact: a contact will not run concurrently down multiple branches.
  • Switching back to Standard Builder: remove Trigger Go-To, Delinked nodes, and Disabled nodes first.

How to draw a Go-To connection

  1. Click the connector dot on the trigger.
  2. Drag to the connector dot on the target action.
  3. Release. The dashed line confirms the route.

Frequently Asked Questions

Are Go-To Connections for Triggers available in the Standard Builder?
No. They are exclusive to Advanced Builder. Switch back to Standard only after removing all Advanced-only features.
What happens to a trigger I never connect?
It auto-connects to Root, but explicitly set its start action so the path is intentional.
Can a contact run two trigger branches at once?
No. The workflow enforces single enrollment per contact, so only one branch runs per enrollment.
Can an action have two incoming connections?
No. Each action accepts one incoming connection. A new connection overwrites the existing one.
How do I change which action a trigger starts on?
Delete the dashed Go-To and drag a new one to the desired action. The change takes effect immediately on save.

Was this article helpful?