Fire actions automatically — or queue them for approval — every time a job moves between stages.
Stage triggers turn your job pipeline into an engine. Every time a job moves from one stage to another, a trigger attached to that transition can fire its action — either running it on its own or queuing it for a person to approve first. Configure them once and the routine follow-through happens without anyone remembering to do it.
§How triggers are organized
There are 26 stage-transition triggers, grouped by the transition they watch — from one stage, to another. Each trigger carries two controls: a mode (PROPOSE, AUTO, or DISABLED) and an on/off switch. The switch lets you park a fully configured trigger without losing its mode, then bring it back exactly as it was.
§The three modes
| Mode | What happens on the stage move |
|---|---|
PROPOSE | The action is drafted and queued for someone on your team to review and confirm. Nothing happens until a person approves it. |
AUTO | The action runs on its own the moment the stage changes — no review step. |
DISABLED | The transition is ignored. Nothing fires. |
§What fires a trigger
Triggers fire on real stage moves — when someone taps a stage dot on the customer's TIMELINE StageJourney tracker or in the Active Job widget and confirms the advance. Every stage change is also recorded in the customer's timeline feed, so you can filter with the STAGES chip to see exactly when transitions happened.
§Who can change them
Editing is admin-only. Non-admins can open the screen and see how every trigger is configured, but the controls are read-only for them — useful for a rep who wants to know what will happen before advancing a stage.
PROPOSE mode. You get the automation's output with a human checkpoint in front of it, and once you trust what it produces, promote it to AUTO.§Related
- ◆See "The automation hub" in this category.
- ◆See "Customize and advance stages" in the JOBS + STAGES category.