HighLevel's own support page, dated June 19, 2026, lists 91 workflow triggers across 14 categories. Most businesses will build on only a handful.
The GoHighLevel workflow triggers worth learning first are the ones that fire when a lead shows up, replies, books or moves through a pipeline.
The rest are specialised: course enrolments, affiliate sales, community leaderboards. They matter if you sell those things, and not before.
Which GoHighLevel workflow triggers matter most
Five groups cover the everyday sales and follow-up work: Events (form submissions and replies), Contact (tags), Appointments, and Opportunities. Payments and Ecommerce Stores join them once money changes hands inside the platform.
Here's how HighLevel's list breaks down, with the trigger most small businesses reach for in each.
| Category | Triggers in it | The one to start with |
|---|---|---|
| Events | 24 | Form Submitted |
| Contact | 12 | Contact Tag |
| Appointments | 4 | Customer Booked Appointment |
| Opportunities | 5 | Pipeline Stage Changed |
| Payments | 12 | Depends on your billing setup |
If you're still choosing what to automate, our overview of the automation workflows you can build in GoHighLevel shows what sits on the other side of these triggers.
Form Submitted: the starting point for most lead flows
This trigger fires when a specific form is submitted, and the only filter is which form. That's enough to separate a quote request from a newsletter signup and send each down its own path.
HighLevel's Form Submitted documentation describes lead qualification, event registration and feedback collection as typical uses. One workflow can watch several forms, and every submission starts its own run.
Forms built outside HighLevel are the catch. They need an integration or a webhook to reach the trigger, so a form on a separate tool won't start anything on its own.
Contact Tag as the glue between workflows
Tags are how one workflow hands a contact to another. The Contact Tag trigger fires when a tag is added, removed, or either, and without a filter it reacts to both.
Tag changes can come from the contacts list, from workflow actions, from CSV imports and from tools like Zapier. The Contact Tag trigger page adds that third-party tools can only add tags, never remove them.
Because a workflow can itself add or remove tags, you can build a loop by accident. Say a workflow reacts to the tag "hot lead" and also writes that tag: it will keep starting itself. Give each tag one job and decide which workflow owns it before you build.
Customer Replied turns answers into actions
A reply is about the clearest buying signal a contact can send, and this trigger lets you act on it immediately. It fires when a contact answers a message and can narrow by phrase, tag, intent type, the workflow that sent the message, and reply channel.
HighLevel's Customer Replied guide gives examples such as creating a sales opportunity when a reply contains words like "interested" or "pricing". Live Chat replies can also be routed into a support queue.
One note: the All-in-One Chat option appears in this trigger's Reply Channel filter, and not every trigger supports it.
Appointment triggers and the re-entry setting
Photo by https://kaboompics.com/ on Pexels
Customer Booked Appointment starts a run when someone books, and a status trigger covers changes such as rescheduling. Recurring appointments don't enter through the booking trigger at all.
Cancellations and reschedules are where reminder flows break. According to HighLevel's page on appointment scenarios in workflows, a status change from New, Confirmed or Show to Cancel, Invalid or No Show counts as cancelled, and the contact is pulled out of the workflow with no further actions.
A change to the start or end time counts as a reschedule. The contact leaves the current run and comes back only if Allow Re-entry is switched on in the workflow settings and the new appointment matches the trigger.
If your reminders go quiet after a client moves their booking, check that setting first.
Opportunity triggers for pipeline follow-up
Five triggers cover the pipeline: Opportunity Created, Opportunity Status Changed, Pipeline Stage Changed, Stale Opportunities, and a second status-based option. HighLevel describes them on its Automating Opportunities page.
Stale Opportunities is the one most teams skip and shouldn't. It catches deals with no change for a number of days you choose, which is a ready-made nudge for a quote that went cold.
There's a constraint on filtering. You can only filter on opportunity fields when the workflow has an opportunity-based trigger, so a workflow started by a form can't branch on deal value in the trigger itself.
When a trigger doesn't fire
Nearly every missed trigger traces back to the event not matching what the trigger expects. The form was on a tool that never sent a webhook, the booking was recurring, the contact was already inside the run with re-entry off, or a filter was set on a field the trigger type can't see.
Work through those four before rebuilding anything. They're cheaper to check than a rewritten workflow.
Tag races are the fifth cause. When workflows modify tags themselves, extra runs can start unintentionally, which looks like a trigger firing when it shouldn't.
Getting these small details right is most of what separates a lead flow that works from one that quietly drops contacts. It's the same groundwork we cover in GoHighLevel CRM setup for small business, and it's where our AI and automation work usually starts.
Once the triggers behave, the wider picture in CRM automation for small business shows where to extend them next.
Frequently asked questions
How many workflow triggers does GoHighLevel have?
HighLevel's support page, dated June 19, 2026, counts 91 triggers across 14 categories. Events is the largest group by a wide margin.
Can a form from another tool start a workflow?
Yes, but it needs an integration or webhook to capture the submission. Without one, the Form Submitted trigger has nothing to react to.
Can Zapier remove a tag and trigger a workflow?
Not for removal. Third-party tools like Zapier can add tags only, so a workflow that waits for a tag to be removed has to get that removal from inside HighLevel.
Why didn't a rescheduled appointment restart my reminders?
A reschedule pulls the contact out of the current run. They only re-enter if Allow Re-entry is on and the new appointment matches the trigger.
Why can't I filter on deal value in my workflow trigger?
Opportunity fields are available in filters only when the workflow has an opportunity-based trigger, such as Pipeline Stage Changed.
Cover photo by Jakub Zerdzicki on Pexels
Sources
- A List of Workflow Triggers — HighLevel Support Portal
- Form Submitted Workflow Trigger in HighLevel — HighLevel Support Portal
