Skip to main content
A trigger starts one workflow when an event happens on another, with no manual run or external scheduler. Use triggers to chain workflows, such as a detail extraction that runs whenever a listing workflow finishes. A common pattern is content that publishes at an unpredictable time, such as a report you want as soon as it’s out. Point a monitor at the page, and add a Data changed trigger that starts the downstream workflow when the report appears. The Triggers tab of a workflow, listing outgoing and incoming triggers

​
Create a trigger

  1. Open the source workflow and select Triggers in the side rail, then Add trigger.
  2. Choose when it fires: Data changed, Workflow finished, or Export completed.
  3. Select the workflow to run, then Create trigger.
To pause a trigger without deleting it, switch it off.
The target runs the next time the event fires.

​
What you’ll see

  • Workflows with triggers show a lightning icon and a count in the workflow list.
  • The Triggers tab lists outgoing triggers and, below them, incoming triggers: the workflows that start this one.

​
Limits

  • Up to 5 triggers per workflow.
  • A workflow can’t trigger itself.
  • Real-time workflows can’t be targets.
  • Source and target must belong to the same team.
  • A triggered run only starts if the target is active, not already running, and has no open support case. Events that arrive mid-run are skipped, not queued.
  • Chains go up to 15 levels deep, which prevents loops.
For time-based runs, see Scheduling. To be notified of these events instead, see Notifications.