Home/HighLevel/Troubleshooting/Zapier trigger
Troubleshooting · Integrations
Fix: GoHighLevel Zapier trigger not working. Connection, subaccount, Zap on.
Zapier problems usually come from the LeadConnector connection, the wrong subaccount selected, the Zap being off, or two automations stepping on each other.
The short answer
A GoHighLevel Zapier trigger usually fails because the LeadConnector connection expired, the Zap points to the wrong subaccount, the Zap is turned off, or another automation already handles the same event, so reconnect LeadConnector, select the right subaccount and test with fresh data.
Michael is a sponsored HighLevel affiliate. Links to HighLevel use his partner link at no extra cost to you. HighLevel prices and product facts on this page come from HighLevel's own pricing page and help center, checked on the date above.
Causes
Why is a Zapier trigger not working with HighLevel?
Most cases come down to the four causes in this table. Check each one before you change anything.
| Cause | How to check |
|---|---|
| Expired connection | Zapier connected accounts |
| Wrong subaccount | Zap account selection |
| Zap off | Zap status |
| Overlapping automation | HighLevel workflows doing the same |
Diagnose
How do you confirm why the Zap did not run before you rebuild it?
Open the Zap history in Zapier and look at the time the event happened in HighLevel. No run at all means Zapier never heard about the event, so the trigger is the problem. A run that stopped with an error means the trigger worked and a later step failed, which is a question for the other app.
For a trigger problem, check the Zap is switched on. Then open the trigger step and look at the account. HighLevel appears in Zapier as LeadConnector, and you select a subaccount when you connect. Agencies with many clients pick the wrong one easily, so read the name under Accounts. If the connection has expired, sign in again with your HighLevel email and password and select the subaccount.
Then test with something new. In the Zap editor, test the trigger and see whether Zapier pulls a sample record. Do the real thing once in HighLevel, such as moving a test opportunity to a new stage for a Pipeline Stage Changed trigger, and watch the Zap history. Check that the trigger event you picked matches what really happens in the account.
Fix
Fix it step by step.
- Reconnect LeadConnector in Zapier.
- Select the correct subaccount.
- Turn the Zap on.
- Test the trigger with fresh data.
- Check for workflows doing the same job.
Still stuck
When to contact support.
If none of these fix it, open Help and Support from the question mark at the top right of your agency view, then start a chat (AI Support Chat or Agent Chat), join a Zoom call or open a ticket. Have your Agency Relationship Number and the Location ID of the subaccount ready, add screenshots of the problem, and turn on Support Access so the team can look inside the account. Only Agency Admins and Agency Users can reach HighLevel support; subaccount users go through their agency.
- Name Zaps by client and job
If the LeadConnector trigger never fires with the right subaccount connected and the Zap on, send support the subaccount, the trigger event, the time of the test and a screenshot of the Zap history.
For prevention, name every Zap after the client and the job, and check whether a workflow already does the same thing. A Zap plus a workflow creating the same contact causes duplicate contacts. Many jobs do not need Zapier at all: webhooks and native connections are usually faster and do not cost Zapier tasks. See connect Zapier, the Zapier integration page and fix a webhook not firing.
Not sure what counts as a trigger? See the glossary entry for trigger. Not on the platform yet? The GoHighLevel 30 day trial through Michael's link lets you set this up and test it before the first invoice. Agencies that want the top plan can read about the Founder Plan.

If a webhook can replace the Zap, it is one less thing to break.
Questions
Common questions.
Why is my Zapier trigger not working?
A Zapier trigger usually fails because the LeadConnector connection expired, the Zap points to the wrong subaccount, the Zap is turned off, or another automation already handles the same event, so reconnect LeadConnector, select the right subaccount and test with fresh data.
How do I prevent it?
Name every Zap after the client and the job, and check whether a workflow already does the same thing. A Zap plus a workflow creating the same contact causes duplicate contacts. Many jobs do not need Zapier at all: webhooks and native connections are usually faster and do not cost Zapier tasks.
When should I contact HighLevel support?
Contact support once you have checked every cause on this page and it still fails, or when the fix sits on HighLevel's side. If the LeadConnector trigger never fires with the right subaccount connected and the Zap on, send support the subaccount, the trigger event, the time of the test and a screenshot of the Zap history.
What is HighLevel called in Zapier?
HighLevel appears in Zapier as LeadConnector. Choose LeadConnector as the trigger or action app, sign in and select the subaccount.
Why is my Zap connected to the wrong account?
You select a subaccount when you connect LeadConnector. Check the name under Accounts in Zapier and connect the subaccount the Zap should use.
Do I need Zapier to connect other apps to HighLevel?
Not always. Many tools connect through the HighLevel App Marketplace, inbound webhooks or the API. Use Zapier when nothing else fits.
Next step
See it in your own account. Thirty days, every feature.
Start a 30 day trial through Michael's link, build the first system and test it before the first invoice. Usage fees for phone, SMS, email and AI can apply during the trial.
HighLevel has three plans at a flat monthly price, each with unlimited users and contacts. See what each one includes and what it costs.
Compare the PlansStarter, Unlimited and Founder