GoHighLevel lead not appearing in Contacts? Trace the failure in order.
Do not start by rebuilding the workflow. First prove whether the submission was sent, which location received it, and whether the exact contact exists under another identity.
Fast diagnosis
- Submit one clearly labelled test lead with a unique email address.
- Record the exact time, page URL, form or survey name and expected location.
- Search Contacts by the unique email—not only by name.
- Confirm that the page, form and workflow all belong to the same sub-account.
- Inspect the workflow execution history only after checking the contact record.
1. Prove that the browser sent the submission
Use a fresh test identity and complete every required field. Note any inline validation, success message or redirect. A success message proves only that the front end accepted the action; it does not prove that HighLevel created the contact.
2. Verify the intended location
Agency users can easily inspect the wrong sub-account. Write down the expected location before testing, then confirm the form asset, embedded widget and receiving workflow are owned by that same location. Search the agency view only when you intentionally need a cross-location check.
3. Search for the exact identity
Search Contacts using the unique email and phone used for the test. A contact may have merged into an existing record, been normalized, or appeared under an unexpected display name. Record the returned contact ID when available.
4. Separate contact creation from workflow execution
A workflow can fail even when the contact was created correctly. Check whether the contact exists first. Then inspect enrolment, filters, trigger conditions and execution history. This prevents a workflow problem from being misdiagnosed as failed lead capture.
5. Retest without contaminating evidence
Change one variable at a time and use a new labelled identity for every rerun. Keep the previous failure record instead of deleting it immediately. Your evidence should show the original symptom, the change made and the result of the fresh test.
What counts as a pass?
The exact synthetic identity is found inside the intended HighLevel location, with a creation time consistent with the submission. A generic success screen or a similarly named contact is not enough.