GoHighLevel workflow not triggering: a checklist
Short answer
When a GoHighLevel workflow doesn't run, it's most often still in Draft (saving isn't publishing), the contact doesn't match the trigger's filters, or re-entry is off and the contact already went through once. If the contact did enter but nothing went out, look at DND, the time window and stop on response. Enrollment History and Execution Logs show which one it is.
The checklist, in order
- Is it published?. Draft workflows don't trigger or take actions. Saved and published are not the same thing.
- Did the contact enter?. Automations > Workflows > open the workflow > Enrollment History and Execution Logs. Errors are highlighted; Highlight Contact Path shows skipped steps and errors, and Go To Action jumps to a step.
- Do the trigger filters match?. Check each filter against the contact. The Form Submitted trigger only works with forms built in HighLevel; outside forms need an integration or a webhook.
- Is re-entry off?. With Allow Re-entry off in the Settings tab, a contact can enter only once. Appointment and invoice triggers always allow re-entry.
- Is a time window holding the step?. Steps outside the workflow's Time Window pause and resume at the next allowed time. Internal actions like tags aren't affected.
- Did stop on response end it?. With Stop on Response on, the workflow ends for a contact as soon as they reply.
- Is the contact on DND?. Check the DND section on the contact. With email DND on, every email step skips that contact, and a bounced email turns it on automatically.
- Did you edit a wait step?. Contacts already waiting keep the old timing after you change a Wait step.
Testing it
HighLevel notes that testing a workflow with a contact isn't fully reliable, especially when you reuse the same test contact. Use a fresh contact for each test.
Common questions
- I published it and it still doesn't run. What next?
- Check whether the contact entered in Enrollment History. If they didn't, it's the trigger or its filters. If they did, the Execution Logs show the step that stopped.
- Can a form on my own website trigger a workflow?
- The Form Submitted trigger covers forms built in HighLevel. A form elsewhere needs an integration or an inbound webhook to start a workflow.
Rather we set it up?
We set this up for you as part of a done-for-you package, quoted on a free call.
GoHighLevel rescue
A messy account someone else built, gone through and fixed: duplicate workflows, broken automations, bad data and texts that don't send.
More workflow fixes
GoHighLevel sending duplicate text messages
Usually two triggers firing on one event, re-entry left on, or the same person saved as two contacts.
GoHighLevel workflow Wait step not working, or contacts stuck
Usually the wait is waiting exactly as set: for a reply or event with no timeout, inside an advanced window, or on timing that was edited later.
GoHighLevel workflow Goal Event not firing
Only one goal per workflow, each contact is checked against it once, and the event or filter has to match exactly.
GoHighLevel trigger links not tracking clicks
Usually a pasted URL instead of the trigger link itself, no workflow listening for the click, or a filter pointing at a different link.
GoHighLevel If/Else branch not matching
Usually AND and OR grouped wrong, a field updated in the same second as the check, or data that isn't there when the step runs.
GoHighLevel custom values or fields showing blank in messages
The contact has no value saved, the workflow doesn't supply it (appointment fields need an appointment trigger), or it was typed instead of picked.
GoHighLevel birthday or date triggers firing at the wrong time
The birthday trigger runs at 8 AM in the account's time zone and skips badly formatted dates. Waits set the hour; workflow settings set the time zone.
Related fixes
Facebook lead forms not syncing to GoHighLevel
Usually the person who connected isn't a page admin, LeadConnector lacks Meta's leads access, or the form isn't mapped.
Read the fixGoHighLevel appointment reminders going out at the wrong time
Usually the workflow's time zone, a fixed wait instead of one timed from the appointment, or calendar notifications sending a second copy.
Read the fixGoHighLevel missed call text back not working
Usually the call was "answered" by a cell phone's voicemail before the timeout, or the number isn't A2P registered.
Read the fix
Want GoHighLevel set up and running for you?
Book a free 15-minute call. Tell us what you sell and where your leads come from, new account or the one you have, and we'll tell you what we'd set up, how long it takes and what it costs.