Pipeline Stage Changed Workflow Trigger in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Pipeline Stage Changed trigger fires when an opportunity moves between stages. Use filters for pipeline, stage, assigned user, lead value, status, tag, and lost reason to automate stage-specific actions.

The Pipeline Stage Changed trigger fires when an opportunity moves from one stage to another in a sales pipeline. It is the primary trigger for stage-driven automation: notifying reps, advancing tasks, or kicking off follow-up sequences when deals progress (or regress).

What it does

The trigger activates on any stage transition — forward, backward, or via reassignment. Combined with filters, you can target exactly the transitions that matter to your sales process.

Why it matters

  • Auto follow-ups — notifications fire on stage changes.
  • Less manual tracking — no more babysitting the pipeline view.
  • Better visibility — real-time signals into deal progression.
  • Customizable filters — narrow by pipeline, stage, user, value, or tag.
  • Faster response — outreach and internal alerts happen instantly.

How to set it up

  1. Go to Automation > Workflows.
  2. Click Create New Workflow or edit one.
  3. Click + Add New Trigger and search for Pipeline Stage Changed.
  4. Name the trigger so the purpose is clear.
  5. Add filters (see below) to scope the trigger.
  6. Define actions, click Save Trigger, then Publish.
  7. Test by manually moving an opportunity through stages.

Available filters

Assigned To

Fires only when the matching opportunity is assigned to a specific user. Useful for routing follow-up tasks or rep-specific notifications.

Tag (formerly "Has Tag")

Fires only when the opportunity carries specific tag(s). Use for prioritization or segmentation. Example: "High Priority" tagged deals trigger an executive alert when they advance.

In Pipeline

Restricts the trigger to a single pipeline. Useful when you run multiple pipelines for different products or segments. Example: only fire inside the "Enterprise Sales" pipeline.

Lead Value

Fires based on the dollar value of the opportunity. Example: notify the sales manager whenever an opportunity above $10,000 changes stage.

Lost Reason

Fires when the opportunity moves to Lost and a specific lost reason is assigned ("Price Too High", "Competitor Chosen", "No Response"). Example: when the lost reason is "Budget Constraints", send a flexible-pricing follow-up.

Pipeline Stage

Fires only when the opportunity moves into a specific stage. Example: when an opportunity moves from Negotiation to Closed Won, notify finance.

Status

Fires based on the opportunity status:

  • Open — still active.
  • Won — closed successfully.
  • Lost — did not convert.
  • Abandoned — no longer pursued.

Example: when status flips to Won, fire a customer welcome sequence.

Common workflow actions

  • Notify the assigned sales rep.
  • Update opportunity fields (status, priority, tags).
  • Create a follow-up task.
  • Trigger another workflow for downstream automation.
  • Send an email to the contact.

Frequently Asked Questions

Does the trigger fire when an opportunity is moved manually in the pipeline view?
Yes. Manual moves trigger the workflow as long as filter conditions are met. The trigger does not care whether the move came from a user, an automation, or an API call.
Can I combine multiple filters in one trigger?
Yes. Filters combine with AND logic, so you can require, for example, a specific pipeline AND a specific stage AND an assigned user. This lets you target very narrow transitions.
How does this interact with other opportunity triggers?
Pipeline Stage Changed is independent of Opportunity Status Changed and Opportunity Created. You can run all three in parallel workflows if you need different automations for different events.
What if an opportunity moves backward to a previous stage?
The trigger fires on any stage change, including backward moves, as long as the filters match. Use Pipeline Stage filters to limit it to forward-only transitions if you want.
Can I see a history of past stage changes?
Not via this trigger — it only fires on real-time transitions. To review historical stage moves, open the opportunity and check its activity log.

Was this article helpful?