Take 10 minutes.
Get hours back every week.
Short walkthroughs that turn the platform into your operations team: automated pipelines, instant follow-ups, AI-handled admin. One video, one less thing to do manually.
How Stage Automations Work with Move Deal Actions
Why stage automations do not fire when a Move Deal action moves an opportunity, and how to wire the logic you need directly into your automation chain.
When you move an opportunity into a new pipeline stage, TrustPager runs the automations configured for that stage. But when a Move Deal action inside an automation moves an opportunity, those stage automations do not fire a second time. This is by design — and understanding why makes it easier to build automation chains that behave exactly as you expect.
Why stage automations do not re-fire on a Move Deal action
Imagine an automation on the "Application Received" stage that sends a welcome email and then moves the opportunity to "Processing". If moving to "Processing" also triggered that stage's automations, you could end up with a chain reaction — stage automations firing automations that fire more stage automations, with no natural stopping point.
To prevent this, TrustPager does not dispatch stage automations when an opportunity is moved programmatically by a Move Deal action inside another automation. Stage automations only fire when a person manually moves a card on the pipeline board, or when you explicitly trigger them via the pipeline UI.
The amber notice on the Move Deal action
When you configure a Move Deal action in the automation builder at https://app.trustpager.com/auto/automations, you will see an amber notice on the action card, between the Stage dropdown and the Save button. It reads something like: "Stage automations will not be dispatched for this move."
This is not a warning that something is wrong — it is a reminder that the destination stage's automations will stay quiet. The notice appears at configuration time so you know to wire any additional logic you want directly into this automation, rather than relying on the destination stage to pick it up.
How to build the chain yourself
If you want actions to run after the move, add them to the same automation, after the Move Deal action. The automation builder lets you sequence as many actions as you need — send an email, create a task, update a field, enrol into an Auto Queue — all in one chain.
Example: an automation fires when a form is submitted. You want it to move the opportunity to "Pending Review" and send a confirmation email. Add both actions to the same automation:
- Move Deal — set stage to "Pending Review"
- Send Email — confirmation message to the contact
Both actions run in sequence. The "Pending Review" stage automations stay quiet, so there is no risk of double-sending or looping.
When stage automations do fire
Stage automations fire in two situations:
- A user drags an opportunity card into the stage manually on the pipeline board at https://app.trustpager.com/pipelines
- A user moves the opportunity via the stage dropdown on the opportunity detail page
In both cases, TrustPager shows a confirmation modal listing the automations that will run, and lets users skip individual actions if needed. See https://trustpager.com/help-center/selective-automation-actions for details on that flow.
Combining Move Deal actions with Auto Queues
A common pattern is to move an opportunity and simultaneously enrol the contact into a nurture queue — all from one automation. Add a Move Deal action followed by an Add to Auto Queue action. The queue enrolment fires as part of this automation, independently of the destination stage's configuration. For more on setting up Auto Queues and the Add to Auto Queue action, see https://trustpager.com/help-center/how-to-set-up-auto-queues.
For developers — API field reference
When TrustPager moves an opportunity via a Move Deal action, the internal automation run record includes stage_automations_dispatched: false. This field confirms that the move was processed without triggering the destination stage's automation set. If you are building integrations or inspecting automation run logs via the API, this field is the reliable signal for distinguishing a programmatic move (automation-driven) from a manual stage change (user-driven, where stage automations do fire).
Tip: If you expect stage automations to run after a programmatic move and they are not, this is why. The fix is to add those actions directly to the automation that contains the Move Deal action, not to the destination stage's automation set.
Two ways to
meet FinalPiece.
Talk to Evie right now, or book a real human for a deeper walkthrough. Whichever feels right.
Pick up the phone.
Hear her in 10 seconds.
- RealHer voice passes for human.
- SmartKnows your prices, hours, and trade.
- PatientPolite, attentive, never has a bad day.
Pencil us in.
60 minutes with a real human · Google Meet · Free.