How to Keep Your Team Updated Using the Note Changed Trigger in GoHighLevel

Notes are where the honest version of a customer relationship gets written down. The reason a renewal is wobbling, the thing the client said on the phone that nobody wants in an email, the detail that decides whether the next conversation goes well. In most accounts that information sits on a record where exactly one person will ever see it.

The Note Changed trigger in GoHighLevel fixes that. It starts a workflow whenever an existing note on a contact record is edited, so an update written by a support agent at four in the afternoon can reach the account manager, create a task and update a field before anybody has to remember to pass it on.

What the Trigger Actually Does

Note Changed activates when a note on a contact record is updated or modified. It exists to keep information synchronised and to start follow up work automatically, rather than waiting for somebody to notice.

Two boundaries are worth stating up front, because both come straight from HighLevel's documentation and both catch people out.

First, it fires on edits, not on creation. A brand new note is the Note Added trigger, not this one. If you want both events, put both triggers on the same workflow, since multiple triggers behave as an OR condition and either will enrol the contact.

Second,deleting a note does not fire it. The trigger activates only when a note is changed or updated, and there is no separate deletion trigger to catch the rest. Anywhere an audit trail genuinely matters, treat notes as a communication tool rather than a compliance record.

It also applies to all note changes on a record. You cannot scope it to one note, a note title or a keyword in the body. The available precision comes from filtering on the contact instead.

Note Changed Versus Note Added

These two sit next to each other in the picker and do different jobs. Choosing the wrong one produces a workflow that never fires, with nothing in the interface to explain why.

• Note Added fires when a new note is attached to a contact for the first time. Use it for first touch events: a support agent logging a new issue, a rep writing up a call, an automation writing a record with the Add to Notes action.

• Note Changed fires when an existing note is edited. Use it for progress events: an issue updated with a resolution, a renewal note revised, an account summary expanded after a meeting.

Most teams want both. A support process cares that a note was created, meaning a new issue exists, and that it was later edited, meaning something has developed. Putting both triggers on one workflow covers it, and the actions underneath run identically either way.

Setting Up the Trigger Step by Step

Go to Automation, open the Workflows tab, click Create Workflow and choose Start from Scratch. On the empty canvas, click Add New Trigger, scroll to the Contactgroup and select Note Changed.

Name it next. The field is mandatory, and something like Client Note Updated or Support Note Revised keeps the canvas and your enrollment history readable months later.

Click Add filters to open the picker. On this trigger the standard fields are short: Has Tagand Doesn't Have Tag. Any custom fields on the sub account appear underneath in their own group, which is how you filter on your own data rather than only on tags.

Has Tag restricts the workflow to contacts carrying a specific tag, so a note edit on a VIP client behaves differently from one on a cold lead. Doesn't Have Tag excludes a group, which is the cleaner way to keep churned clients, test records and internal contacts out of a live alerting workflow. The two combine well, and multiple filters use AND logic, so every condition has to be true.

Save the trigger, build your actions, then switch the toggle from Draft to Publish.

The Actions That Make It Useful

A note change on its own is just an event. For this trigger the useful actions are almost all internal rather than customer facing.

• Send Internal Notification.The workhorse. Emails, in app notifications or mobile push to the assigned user, specific users, all users or a custom address. This is what turns a quiet edit into an alert somebody sees.

• Add Task.Creates a dated, assigned task so the update becomes work rather than information.

• Add Contact Tag.Marks the record so a smart list can surface every contact whose notes changed this week.

• Update Contact Field.Writes a status or a last reviewed date so reporting sees the activity without anybody opening the note.

• Assign to User.Routes the contact to a specialist when a note edit signals an escalation.

  

Customer facing actions are possible, and HighLevel's documented use cases include a renewal reminder off the back of a note update. Use them carefully. A note is an internal artefact, and a contact receiving a message every time a colleague tidies their own writing is a bad experience.

Notes That Workflows Write Themselves

There is a second half most people miss. Workflows can write notes as well as react to them, using the Add to Note saction, which adds a note to the enrolled record.

It supports the same rich text editor the Notes interface uses, so bold, italics, underline, strikethrough, lists and hyperlinks all carry through. It also supports an optional note title and colour on contact based workflows, plus merge fields through the custom value picker, so a note can be assembled from live data rather than fixed text.

A booking confirmation note assembled from appointment merge fields gives your team a readable history without anybody typing. One caution: if an automation writes notes and another workflow triggers on note events, you can build a loop. Keep the writing workflows and the listening workflows on clearly separated tags.

Three Workflows Worth Building

1. Support escalation.Trigger on Note Changed with Has Tag set to High Priority. When an agent updates the note on an open issue, assign the contact to a senior specialist, create a same day task and send an internal notification.

1. Account manager alert.Trigger on Note Changed with Has Tag set to Client. Notify the assigned user only, so managers hear about their own accounts and nobody else's, and add a tag so a smart list shows every account touched this week.

2. Renewal watch.Trigger on Note Changed with Has Tag set to Member or Renewal. Create a task for the owner and update a last reviewed date. A revised renewal note is usually the earliest signal you will get that something changed.

Limitations Worth Planning Around

It fires on every note change.No scoping to a particular note or keyword. Precision comes from tag filters on the contact.

Rapid edits fire repeatedly.An agent making three quick corrections generates three enrolments. Manage it with Allow Re-entry on the Settings tab, or a Wait step or If/Else condition so repeated firing does not become repeated notifications.

Deletion is invisible.Only changes and updates fire it. A deleted note passes silently.

Note content is not a condition.You cannot branch on what the note says. If the content genuinely needs to drive the logic, have the person editing the note apply a tag too, and build the rest on the Contact Tag trigger.

Frequently Asked Questions

What happens if a note is deleted instead of updated?

Nothing. This trigger activates only when a note is changed or updated, and deleting a note will not trigger the workflow. There is no separate deletion trigger either, so if you need a permanent audit trail, notes are not the right place to keep it.

Can the trigger handle several note changes in quick succession?

Yes, it activates each time a note is updated, which can mean several enrolments in a row while somebody is editing actively. To prevent overlapping workflows you can add conditions or a cooldown in the actions, or use Allow Re-entry to control repeat enrolment.

Can I combine Note Changed with other triggers in one workflow?

Yes. It works alongside triggers such as Note Added, Contact Tag or Task Completed. Multiple triggers on a single workflow behave as an OR condition, so any one of them enrols the contact and the same actions run underneath.

Can I track changes to a specific type of note?

Not directly. The trigger applies to all note changes on a contact record. You refine the scope with the Has Tag and Doesn't Have Tag filters, which target the type of contact rather than the type of note. Tagging contacts by account type is the usual workaround.

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.