How to Keep Sales Opportunities Updated Automatically Using the Opportunity Changed Trigger in GoHighLevel

A sales pipeline is only as useful as the day it was last touched. Deals get reassigned in a hurry, a quote gets revised upward after a site visit, somebody marks an opportunity Lost on a Friday afternoon, and none of it reaches the people who needed to know.

The Opportunity Changed trigger in GoHighLevel closes that gap. It watches opportunity records for updates and starts a workflow the moment one happens, whether the change was a new owner, a different lead value, a pipeline move, a lost reason or a custom field somebody filled in during a call.

This guide covers what the trigger reacts to, how it differs from the other opportunity triggers, how to configure it filter by filter, and what the three operators actually mean.

What the Opportunity Changed Trigger Does

HighLevel describes it as a trigger that automates actions whenever an opportunity record is updated. The important word is any. Where Opportunity Status Changed only reacts to the status field, Opportunity Changed responds to broader modifications such as lead value adjustments, stage movements, reassignments and custom field updates.

That breadth is what makes it useful and also what makes filters essential. Unfiltered, it fires on every small edit anybody makes. Pointed at one field with the right operator, it becomes a precise piece of plumbing that keeps your CRM honest.

The two benefits owners feel first are comprehensive tracking, because actions can run on any change rather than just a status update, and real time notifications, because the team hears about an update when it lands instead of at the next pipeline review.

How It Differs From the Other Opportunity Triggers

The Opportunities group in the trigger picker holds five entries. Knowing which one to reach for saves a lot of rebuilding later.

Opportunity Created fires once, when the deal first appears. It suits a welcome sequence or stamping a source tag on a new opportunity.

Opportunity Status Changed fires only when the status moves between Open, Won, Lost and Abandoned. It is narrower, and perfectly good when status is all you care about.

Pipeline Stage Changed fires when a card moves from one stage to another, which is more direct if your automation is about stage progression.

Stale Opportunities does the opposite job. It fires when a deal sits in the same stage for longer than you allow.

Opportunity Changed is the wide net across all of it. Reach for it when the change you care about is a field the others cannot see, such as a custom field, the assigned user or the monetary value.

Setting the Trigger Up

Open Automation in the sub account, then create a new workflow or open the one you want to extend. The Workflow List is also where you file automations into folders so they stay findable.

Inside the builder, click Add New Trigger, type Opportunity Changed into the search box, and select it from the Opportunities group.

Then name it. The field arrives prefilled with the trigger's own name, which tells you nothing once a sub account holds thirty workflows. Something like Deal Reassigned Alert says what the automation is for at a glance.

Underneath the name sits the Add filters link. Everything that makes this trigger precise lives behind it, so it is worth understanding the operators before choosing fields.

The Three Operators That Change Everything

Most filters here offer the same three operators, and picking the wrong one is the most common reason a workflow either never fires or fires constantly.

Has changed fires when the field moves to any other value. Use it when the fact that something moved is the news, such as any reassignment at all.

Has changed to fires only when the field changes to the specific value you select. Status has changed to Won, or lost reason has changed to Price Too High.

Equals is the subtle one. It fires when any change happens on an opportunity that currently holds the value you selected. It is not watching that field for movement, it is using that field as a condition on the record.

Has changed to is usually what people mean when they reach for Equals, and reading the difference now saves an afternoon later.

Every Filter You Can Apply

Assigned to watches ownership. Has changed catches any handover, has changed to catches deals landing with one named rep, and equals watches every change on that rep's deals.

Tag controls the trigger with opportunity tags, so automation only runs when a deal carries something like Hot Lead. Its operators are Equals to, Not Equals to, Any of and None of, which makes it the natural filter for priority tiers.

In pipeline keeps the workflow inside one pipeline. If you run separate sales, onboarding and retention pipelines, this is the filter that stops one workflow shouting about all three.

Lead value is the money filter, and it behaves differently. Instead of change operators it offers numeric comparisons: equals to, greater than, greater than or equal to, is not equal to, less than, and less than or equal to.

Lost reason reacts when a deal is marked Lost and a reason is attached. Has changed to a specific reason is the useful setting, because Price Too High deserves a very different follow up from Went With Competitor.

Status carries four operators rather than three. Alongside has changed and has changed to, there is Is and Is not, which match the current status rather than a movement.

Opportunity custom fields are supported too, and this is where the interesting automation lives. Checkbox fields offer Added, Removed and Equals, so ticking a box such as Contract Signed can start a workflow on its own. Radio select and dropdown fields use has changed, has changed to and equals, and date custom fields are now fully supported with the same three.

Filters combine, so each one you add narrows the trigger further. Adding all six because they look useful is the fastest way to build a workflow that never runs.

Choosing the Actions That Follow

The actions are ordinary workflow steps, and the four HighLevel calls out cover most builds. Send an email or SMS notification so a rep hears about the update. Assign a task so the follow up has an owner. Update the contact record. Or trigger another workflow, which is how a deal change hands off to a full onboarding sequence.

Internal notifications deserve a mention of their own. A short notification to the assigned user, fired on Assigned to has changed, is a two step workflow that takes minutes to build and fixes one of the most common handover failures in a small sales team.

When the actions are in place, click Save Trigger, run a test, then publish. Saving the trigger panel is not the same as saving the workflow, and a workflow left in Draft does nothing while deals keep moving.

Four Automations Worth Building First

Won deal handover.Status has changed to Won, then create an onboarding task, notify the delivery team and enrol the contact in onboarding. Most businesses miss this one, and clients notice it.

Ownership handover.Assigned to has changed, then notify the new owner with the deal name and value and add a task to make contact within a day.

Big deal alert.Lead value greater than a threshold that matters to you, then notify a manager. Revised quotes and upsells stop being invisible.

Lost reason follow up.Lost reason has changed to Price Too High, then wait a few weeks and send a considered check in. Losing on price is not the same as losing forever.

Mistakes to Avoid

Building loops.If the workflow's own actions update the opportunity, that update is itself a change and the trigger can pick it up again. Watch the re entry setting, and prefer writing to the contact rather than back to the same deal.

Using Equals when you meant Has changed to.Equals fires on any change to a record holding that value, which is a much wider net than most people expect.

Leaving the trigger unfiltered.On a busy pipeline that enrols contacts constantly. Add at least one filter before you publish.

Skipping the test.HighLevel's own advice is to update an opportunity by hand, then check the workflow logs to confirm the actions ran.

One reassurance is worth knowing. HighLevel confirms that existing Opportunity Changed workflows keep their current behaviour unless you edit them, so the newer operators and date field support disturb nothing already running.

Frequently Asked Questions

How is this different from the Opportunity Status Changed trigger?

Opportunity Changed reacts to any modification on an opportunity, including assignment, lead value, pipeline, lost reason and custom fields. Opportunity Status Changed only reacts when the status itself moves. If status is all you need, the narrower trigger is simpler.

Does it work with opportunity custom fields?

Yes. Checkbox, radio select, dropdown (single and multiple) and date custom fields are all supported. Checkbox fields use Added, Removed and Equals, and the rest use has changed, has changed to and equals.

What is the difference between Has changed, Has changed to and Equals?

Has changed fires on any value change. Has changed to fires only when the field changes to the value you pick. Equals fires when any change happens on an opportunity that currently holds that value, so it acts as a condition on the record rather than a watch on the field.

Can I combine several filters on one trigger?

Yes, and it is usually the right move. Pairing In pipeline with Status has changed to Won gives you a workflow that only runs for won deals in the pipeline you care about.

Need Expert Help with GoHighLevel?

New to GoHighLevel and ready to get started? Buy your GoHighLevel account here and launch with confidence.

Already know what you need and want our team to handle everything, from complete setup and customization to funnels, workflows, automations, CRM, and pipelines? Click here.