Loom Video to Watch:
Why use Zapier
Use a Zapier webhook to send Lead Hacker leads into GoHighLevel (GHL), set up per campaign. New native GHL connections are currently blocked because GHL deprecated a function the integration relied on. Existing connections still work, and the dev team is fixing it.
Zapier is the recommended setup even after the fix. The native integration connects at the client level only, so each client can link one GHL account and every campaign under that client goes to the same place. A campaign-level webhook lets you route each campaign separately, tag leads by campaign, and add them straight to a pipeline or automation without relying on GHL tag triggers.
Make.com works the same way if you prefer it: catch the webhook, then create the contact in GHL.
Before you start
A Zapier account on a plan that includes Webhooks by Zapier (a premium app, not on the free plan)
Access to the client's campaign in Lead Hacker
Login access to the client's GoHighLevel sub-account
The campaign name you'll use as the tag in GHL
Optional: the GHL pipeline or workflow you want new leads added to
Part 1: Create the Zap and get the webhook URL
Log in to Zapier and click Create > Zap.
Rename the Zap so it's easy to find later, for example Lead Hacker > GHL | [Client] | [Campaign name].
For the trigger, search for and select Webhooks by Zapier.
Under Trigger event, choose Catch Hook, then click Continue.
Leave "Pick off a Child Key" blank and click Continue.
Copy the webhook URL Zapier shows you. Keep this tab open; you'll come back to it in Part 2.
Part 2: Add the webhook to the campaign in Lead Hacker
Set this up on the campaign, not the client. The client-level webhook is what failed on the Sept 30 call: Zapier said "successfully" but never recorded the lead.
In Lead Hacker, open the client, then open the specific campaign you want to send to GHL.
Go to the campaign's integration / webhook settings. (Add screenshot: exact menu path.)
When asked where to connect, select Campaign (not Client).
Paste the Zapier webhook URL from Part 1 and save.
Click Send test lead.
Go back to Zapier and click Test trigger. You should see a request with the test lead's details (name, email, company and so on).
Select that request and click Continue with selected record.
Part 3: Send the lead into GoHighLevel
In Zapier, click + to add an action and search for LeadConnector (GoHighLevel's app in Zapier).
Choose the action event Create/Update Contact, then click Continue.
Connect the account: sign in to GHL and pick the client's sub-account. Click Continue.
Map the fields from the test lead into the GHL contact fields:
First name, last name
Email
Phone
Company name
Any other fields the client needs (job title, LinkedIn URL, website)
In the Tags field, type the campaign name. This tags every lead with where it came from, so the client can sort and trigger on it.
Click Continue, then Test step.
Open the GHL sub-account and confirm the test contact is there with the campaign tag.
Part 4: Add automations, publish, and repeat
Optional: add to a pipeline. Add another LeadConnector action, Create/Update Opportunity. Pick the pipeline and stage, and map the contact from Part 3.
Optional: start an automation. Add a LeadConnector action to add the contact to a workflow (or campaign) in GHL. This replaces relying on tag triggers inside GHL.
Test each extra step, then click Publish to turn the Zap on.
Send one more test lead from Lead Hacker and confirm it lands in GHL end to end.
Repeat for each campaign. Build one Zap per campaign (duplicate this Zap to save time), then change the webhook URL in Lead Hacker, the GHL sub-account, and the campaign tag.
Troubleshooting
Problem | Likely cause | Fix |
Zapier says "successfully" but no webhook request is recorded | Webhook was added at the client level | Remove it and add it on the campaign instead (Part 2) |
Test trigger finds nothing | No test lead was sent after saving the URL | Click Send test lead in Lead Hacker, then Test trigger again |
Leads from different campaigns all land in one GHL account | Using the native client-level integration | Use one Zap per campaign with its own tag |
Native GHL integration won't connect | GHL deprecated the function it uses; new connections are blocked | Use this Zapier setup; devs are fixing the native option |
Contact is created but has no tag | Tags field left empty in the LeadConnector step | Add the campaign name in Tags and re-test |