Workflows - Go-To Connections for Triggers

Go-To connections for triggers lets you point each trigger to the exact action where its path should begin—right on the canvas. It keeps complex entry logic tidy without duplicating workflows or building giant if/else stacks.

What it does

• Set a start action per trigger. Drag a dashed Go-To connection from the trigger to the action where that trigger should begin.

• Clean visual routing. Trigger Go-To links are dashed with an arrowhead; normal sequential paths stay solid.

• Direct execution. When a trigger matches, the workflow jumps directly to its connected start action and continues from there.

Example

You can set multiple Go-To connections for each trigger, allowing you to define exactly where a contact should start when that specific trigger fires.

Access & availability

• Where: Open a workflow → Advanced Builder → select a trigger on the canvas.

• Availability: A Go-To connection for the triggers will be visible when the trigger is connected to an action other than the Root (first) action

Key behaviors & visual cues

• Dashed connector: Trigger Go-To appears as a dashed line with arrowhead from the trigger to its start action.

• Default (“dangling”) behavior: If a trigger has no Go-To set, it auto-connects to the Root (first) action.

• Save rule: Every trigger must connect to exactly one action to save the workflow; reassign any time by dragging the dashed connector.

• Execution: Matching the trigger sends the contact straight to the target action; the rest of the path runs normally.

How to set it up (step-by-step)

1. Open Advanced Builder. Add/position your triggers and actions on the canvas.

2. Create the route. Select a trigger → drag the dashed Go-To connector from the trigger to the action where it should start.

3. Reassign if needed. Drag the same dashed connector to another action.

4. Save → Publish. Changes follow the usual draft → publish model.

Additional 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 you should explicitly set the correct start action.

• Single enrollment per contact. A contact won’t run concurrently down multiple branches in the same workflow.

• Switching back to Standard Builder. Remove Advanced-only features (Trigger Go-To, Delinked nodes, Disabled nodes) before switching views.

• Draft → Publish. Routing changes don’t affect live execution until you Publish.