New Operators for Opportunity Changed

How It Works

The Opportunity Changed trigger now supports event based operators, so you can be more specific about what change should actually fire a workflow.

Previously, this trigger mainly checked whether an opportunity field equals a value. That meant workflows could run over and over on updates where the value did not actually change.

Now you can tell ESC Hub to trigger only when a field:

• Has Changed

• Has Changed To (a specific value)

• Equals (still available)

This applies to key standard opportunity fields like:

• Assigned To

• In Pipeline

• Status

• Lost Reason

And it also expands what you can do with custom fields, including options like:

• Added and Removed for checkbox fields

• Has Changed and Has Changed To for radio select, dropdowns, and date fields

How to Use

1. Go to Workflows and open the workflow you want to update (or create a new one).

2. Add a trigger and select Opportunity Changed.

3. Choose the field you want to monitor (standard or custom).

4. Pick the new operator that matches what you need, for example:

   • Has Changed if you only care that it changed

   • Has Changed To if you only want it to run when it changes to a specific value

   • Added or Removed if you are tracking checkbox style custom fields

5. Save and publish your workflow.

Why This Matters

This is one of those small changes that prevents a lot of messy automation.

With the new operators, your workflows can run only when something truly changes, which means:

• fewer accidental triggers

• cleaner reporting and attribution

• less noise for your team

• fewer duplicate tasks, emails, or internal notifications firing for no reason

Example:
If you want a workflow to run when Assigned To changes to John, you can now use Has Changed To: John. That means it will only trigger when it actually changes to John, not every time the opportunity is updated while already assigned to John.

Use Cases

Notify the right person when ownership changes
Trigger an internal notification only when Assigned To has changed, or only when it has changed to a specific user.

Pipeline and stage automation without duplicates
Run actions only when an opportunity moves pipeline or changes status, instead of firing on every edit.

Lost reason follow up that only runs once
Trigger a workflow only when Lost Reason has changed to a specific reason, so you can tag, report, or start a reactivation sequence.

Custom field based workflows that are actually reliable
Use Added and Removed for checkbox fields, or Has Changed To for dropdowns and radio selects, so your workflows match real customer actions.