GoHighLevel Leads Stopped Coming In? Check These 3 Things in Order
When GoHighLevel leads stopped coming in after a build went live, check three things in this order: was a contact created, did the workflow fire, and did it fire but do nothing. Each answer points to a different fix, and HighLevel's own tools (the form's Submissions tab, Enrollment History and Execution Logs) show you which one it is (HighLevel, HighLevel).
Don't rebuild the workflow first. Follow one lead through it.
Where this came from
On Nov 3 a poster in r/gohighlevel asked what breaks after a GHL build goes live. They said "leads stopped coming through" turns out to be a different cause each time, listed the same three step check order, and described one case where a form field renamed on the client's site broke the mapping silently (Reddit).
Single-source: that's one post summarizing other threads, and we didn't read the replies. The check order holds up against HighLevel's help docs, which is what the steps below are built on.
What the top guides leave out
The top results for this search are good debug lists (Pathsentra, Your HighLevel Expert, eArif, ClickToClose, Insert Fuel). Most of them assume you built it and you broke it. After a handoff, the change usually happened somewhere you weren't looking. A few things they skip or only mention in passing:
- Changes made on the client's side. Embed codes are static, so form changes don't reach the site until someone pastes new code (HighLevel). External form field mapping can drift when the client edits their site form (HighLevel, Reddit, single-source).
- Snapshot refreshes. If a refresh removes steps in a snapshot-linked workflow, contacts waiting on a deleted step can be removed (HighLevel).
- Who owns the fix three months later. The Reddit poster said few people mention it (Reddit, single-source). None of the top five guides we read covers handoff ownership.
Step 1: Was a contact created?
Submit one test lead with a brand-new email and a phone you control. Then open Sites > Forms > the form > Submissions (HighLevel, AIBrevo).
No submission at all. The form never reached HighLevel. Example: you changed the form's layout or deactivation settings, but the client's site still runs the old embed code. HighLevel says embed codes are static and changes need a new code pasted in (HighLevel).
A submission, but the contact is blank or missing fields. For forms on the client's own site, check Settings > External Tracking > Settings, open the domain, and click Map fields. Pick the right CRM field for each input and save (HighLevel). Example: one r/gohighlevel user saw new contacts arrive blank, with the form data sitting under "Unmapped Fields" in contact activity (Reddit, single-source). A renamed field on the client's site is the cause the Nov 3 poster described (Reddit, single-source).
A submission, but no new contact. Search Contacts for the exact email and phone. With Allow Duplicate Contact turned off, a matching email or phone updates the existing contact instead of creating a new one (HighLevel). Example: a returning customer fills the form again, gets merged into their old record, and nothing looks new.
Step 2: Did the workflow fire?
Open the workflow and check the Draft/Publish toggle first. Draft mode means it won't trigger for real (HighLevel).
Then open Execution Logs and Enrollment History and look for your test contact (HighLevel). If they aren't there, check:
- The trigger filters. HighLevel's troubleshooting steps say to confirm the contact meets every trigger condition and filter (HighLevel). Example: a Form Submitted trigger set to one form won't fire for a rebuilt copy of it, since rebuilt forms get new IDs (Your HighLevel Expert, single-source).
- The trigger type. If the contact was merged into an existing record, a Contact Created workflow won't trigger again (HighLevel). Example: the welcome workflow is quiet for repeat leads, while a Form Submitted trigger would still catch them (AIBrevo, single-source).
- Re-entry. HighLevel says to test with a fresh contact and check whether re-entry is allowed when you expect repeat enrollment (HighLevel).
Step 3: Did it fire but do nothing?
If the contact entered, click Highlight Contact Path. The builder shows the path they took, nodes with errors, skipped nodes, and entry and exit status (HighLevel).
Read the exit status in Enrollment History. "Removed by External Workflow Action" means a different workflow pulled the contact out (HighLevel). Example: a cleanup workflow the client added removes new leads before the follow up sends.
Look for "Removed by - Snapshot Refresh" too. It appears when a snapshot refresh deleted the step a contact was waiting on (HighLevel).
Shortcut: if a message went out but looked wrong, go to Conversations, open the message details, and click the workflow link. It opens Execution Details for that exact run (HighLevel).
Decide who fixes it next time
Write down who gets the call when leads stop, and keep the test contact you used so the next check takes minutes. If you still need HighLevel support, its docs ask for the affected contact, workflow name, approximate test time, screenshots and execution or error details (HighLevel).
FAQ
Why did my GoHighLevel leads stop coming in when nothing changed? Something usually did, just not inside the workflow. Embed codes are static, so form edits don't reach the site until the code is replaced (HighLevel), and a snapshot refresh can remove contacts from deleted steps (HighLevel).
The form submitted but no new contact showed up. Why? With Allow Duplicate Contact off, a matching email or phone updates the existing contact instead (HighLevel).
Contacts arrive blank from my client's website form. What's wrong? Check field mapping under Settings > External Tracking and map each input to a CRM field (HighLevel).
Where do I see if a workflow ran for one contact? Automations > Workflows > open the workflow > Execution Logs, then View Details (HighLevel).
Why didn't my Contact Created workflow fire for a repeat lead? If the lead merged into an existing contact, that trigger won't fire again (HighLevel).
How should I test after fixing it? Use a fresh contact that hasn't entered the workflow before (HighLevel).
Follow @TheoAITools