GoHighLevel Workflow Not Triggering? Fix Checklist

In short

The two most common reasons a GoHighLevel workflow does not fire are that it is still in Draft instead of Published, and that the trigger filters are too narrow so no contact qualifies. Other causes include re-entry being blocked, a missing email or phone field, DND or quiet hours, and a trigger type that does not match the real event.

• Check the publish state first: a Draft workflow never runs, no matter how correct the rest is.
• Then check the trigger filters: one wrong condition can silence the whole workflow.
• Open Enrollment History on the workflow to see if any contact entered at all.

How do you find out why a GoHighLevel workflow is not triggering?

Open the workflow under Automation > Workflows. Work down this checklist in order, from the cheapest fix to the rarest. Each cause below tells you where to look and what to change.

The fastest single clue is the Enrollment History tab on the workflow. It lists every contact that entered. If it is empty, your problem is the trigger or the publish state, not the actions inside. If contacts entered but nothing happened next, your problem is a later step or a send setting like DND.

Is the workflow published, or still in Draft?

This is the number one cause. A workflow saved in Draft looks finished but never runs. New workflows and new edits both default to Draft until you publish them.

How to check: open the workflow and look at the toggle in the top right. It reads Draft or Published. How to fix: flip it to Published, then save. Any change you make after that also needs a re-publish before it goes live.

Are the trigger filters too narrow or wrong?

A trigger with filters only fires for contacts that match every filter. One extra condition, a wrong tag name, or a value that no contact actually has, and nobody qualifies. The workflow is live but silent.

How to check: click the trigger and read each filter line out loud. Ask if a real contact could pass all of them at once. How to fix: remove filters you do not need, correct tag or field names to match exactly, and test with one contact you know should qualify. Empty Enrollment History plus a Published workflow almost always means the trigger filters are the problem.

Is re-entry blocked because the contact is already in the workflow?

By default a contact can only be in a workflow once. If your test contact already went through, the trigger will not pull them back in, so it looks broken when it is working as designed.

How to check: open the workflow Settings tab and find the Allow Re-Entry option. Then check Enrollment History to see if that contact is already listed. How to fix: turn on Allow Re-Entry if your use case needs the same contact to run more than once, or test with a fresh contact that has never entered.

Is the contact missing the email or phone the trigger needs?

Some triggers and actions need a specific field to work. An email step does nothing for a contact with no email. A trigger watching for a form with a phone field will skip a contact that has no phone. The workflow does not error, it just quietly passes them by.

How to check: open the contact record and confirm the field the trigger or action depends on is filled in. How to fix: require that field on the form or import that feeds the workflow, so every contact arrives with the data the workflow needs.

Is DND or quiet hours blocking the messages?

Here the workflow triggers fine and the contact enters, but no message goes out. DND (Do Not Disturb) on the contact blocks sends. Quiet hours or a sending window set on the workflow can hold messages until later, which can look like nothing happened.

How to check: open the contact and look for the DND flag on email or SMS. Then check the workflow Settings tab for a sending window or quiet hours setting. How to fix: clear DND if the contact should receive messages, and widen or remove the sending window if messages are stuck waiting.

Does the trigger type match the real event, and are you testing live?

A trigger only fires on the exact event you picked. A Form Submitted trigger will not fire when you add a tag by hand. A Tag Added trigger will not fire on a calendar booking. If the event you are testing is not the event the trigger listens for, nothing happens and nothing is wrong.

How to check: match your test action to the trigger type one for one. If the trigger is Form Submitted, actually submit that form. How to fix: pick the trigger that matches the event you want, or trigger the real event instead of a stand-in. Also confirm you are testing on the live published version, since edits in an unpublished draft do not run for real contacts.