Opportunity Changed Workflow Trigger in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Opportunity Changed trigger fires when any field on an opportunity updates, not just status. Filter by assignment, pipeline, lead value, tags, status, or custom fields to control exactly when workflows run.

The Opportunity Changed trigger reacts to any update on an opportunity record — assignments, pipeline moves, lead value shifts, tag changes, custom fields. It is broader than Opportunity Status Changed, which only fires on status updates.

What It Catches

  • Reassignment to a different user.
  • Pipeline movement.
  • Lead value changes.
  • Status updates.
  • Tag additions or removals.
  • Custom field updates (checkbox, radio, dropdown, date).

Configure the Trigger

  1. Go to Automations > Workflows. Open an existing workflow or create one.
  2. Click + Add New Trigger and search for Opportunity Changed.
  3. Give the trigger a clear name so you can find it later.
  4. Add filters to scope when the trigger fires (next section).
  5. Add actions: send SMS, send email, assign a task, update the contact, fire another workflow.
  6. Click Save Trigger, run a test, then Publish.

Filter Operators

OperatorBehavior
Has ChangedFires when the field changes to any new value.
Has Changed ToFires only when the field changes to the specific value you select.
EqualsFires when any change happens on opportunities that currently match the selected value.

Available Filters

Assigned To

Fires when an opportunity is reassigned. Use it to notify the new owner, kick off a handoff sequence, or update internal records when a high-value lead moves to a senior rep.

Tag

Filter by tags on the opportunity. Combine with other filters to fire workflows only when, for example, a lead tagged Hot Lead moves stages.

In Pipeline

Scope the trigger to a specific pipeline. Useful when sales, onboarding, and retention each run their own pipeline and you do not want cross-firing.

Lead Value

Fires when the monetary value increases or decreases. Notify reps on upsells, alert account managers on downward revisions, or fire retention sequences on dropped value.

Lost Reason

Fires when a Lost reason is set or changed. Send a discount follow-up when the reason is Price Too High, or trigger a feedback workflow on other reasons.

Status

Operators include Is, Is Not, Has Changed, and Has Changed To. Trigger only on Won, exclude Abandoned, or fire whenever status moves between specific stages.

Custom Field Filters

  • Checkbox: Added, Removed, Equals.
  • Radio Select: Has Changed, Has Changed To, Equals.
  • Dropdown (single & multi): Has Changed, Has Changed To, Equals.
  • Date: Has Changed, Has Changed To, Equals.

Test Before Publishing

Manually update an opportunity that should match the filters. Confirm the workflow runs and the actions complete. Review workflow logs for any failed steps before flipping to Publish.

Frequently Asked Questions

How is this different from Opportunity Status Changed?
Opportunity Status Changed only fires on status updates (Open, Won, Lost). Opportunity Changed fires on any field update — assignment, pipeline, lead value, tags, custom fields, or status.
Can I combine multiple filters?
Yes. Stack filters to scope tightly — for example, fire only when a lead tagged Hot Lead in the Sales pipeline gets reassigned to a senior rep.
What's the difference between Has Changed and Has Changed To?
Has Changed fires on any new value. Has Changed To fires only when the field becomes a specific value you pick.
Does the trigger work with custom fields on opportunities?
Yes. Checkbox, radio, dropdown (single and multi), and date custom fields all support filters.
How do I test the workflow?
Manually update a matching opportunity and confirm the workflow runs. Review the workflow logs to catch any errors before publishing.

Was this article helpful?