Home/HighLevel/Troubleshooting/Webhook not firing

Troubleshooting · Developers

Fix: GoHighLevel webhook not firing. Published, right URL, logs.

Inbound webhooks need a sample payload and a published workflow. Outbound webhooks need the right URL and method. The webhook logs show what happened.

  • 5likely causes
  • 5fix steps
  • 1escalation path
SymptomCausesFixConfirm
5
Likely causes5 to check1 ruled out
Diagnosis
Developers · SymptomWebhook not firing
Issue
1Workflow not publishedRuled out
2Wrong URLChecking
3No sample payloadTo check
4Method or auth wrongTo check
5Receiver errorTo check
5 fix stepsPublished, right URL, logs.Fix it, then confirm it works

The short answer

GoHighLevel webhooks usually fail because the workflow is not published, the URL is wrong, an inbound webhook never received a sample payload to map, the method or authorization is wrong, or the receiving server rejected it, and the webhook logs show which one happened.

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 HighLevel webhook not firing?

Most cases come down to the five causes in this table. Check each one before you change anything.

CauseHow to check
Workflow not publishedWorkflow status
Wrong URLCopied URL
No sample payloadInbound webhook mapping
Method or auth wrongCustom webhook settings
Receiver errorWebhook logs response

Diagnose

How do you confirm why the webhook did not fire before you change the workflow?

First decide which kind you have. An inbound webhook receives data: another app posts to a HighLevel URL and starts a workflow. An outbound webhook sends data: a Custom Webhook action in a workflow calls another system. They fail in different places.

For inbound, send one test request to the webhook URL from the other app, then return to the workflow trigger. If the sample payload appears, HighLevel received it and the URL is right. If nothing appears, the other app is posting to the wrong URL or not posting at all, so check its own logs. If the payload arrives but contacts look empty, the fields were never mapped. You cannot map fields HighLevel has not seen, which is why the test payload comes first.

For outbound, open the workflow history and find a contact who should have triggered it. If the contact never reached the Custom Webhook action, the webhook is not the problem. The workflow is in draft or the trigger did not fire, covered in fix a workflow not triggering. If the action ran, read the response in the webhook logs. An error from the receiver points to the method, the headers or the authorization. An unauthorized response from the HighLevel API is covered in fix API 401 errors.

Fix

Fix it step by step.

  1. Publish the workflow.
  2. Copy the URL again.
  3. Send a test payload and map fields.
  4. Check method, headers and authorization.
  5. Read the webhook logs dashboard for responses.

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.

  • Always send a test payload first

If the action runs and the logs show no response at all, send support the workflow name, the action, the destination URL, the time of the run and a copy of the log entry. Remove any secret from what you send.

For prevention, always send a test payload before mapping, send only the fields the other system uses and check the logs after launch. See use webhooks and the Make integration page. If you rely on Zapier instead, see Zapier trigger not working.

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.

Help & Support
Opens from the question mark at the top right of the agency view
Relationship Number0 000 000
1
Support AccessLets support look inside your account for a set time
3
Quick support actions
Start Chat
5
Before you contact supportHave these ready
1
Agency Relationship NumberTop of Help and Support, with a copy button
2
Location ID of the subaccountSettings, Business Profile, or the URL after /location/
3
Support Access turned onAgency Settings, Company, Advanced Settings. It expires on the date you pick
4
Screenshots and the exact errorWhat you did, what you expected, what happened
5
Pick a channelAI Support Chat, Agent Chat, a Zoom call, or a ticket by email
Agency Admins and Agency Users onlyBilling or login: +1 (888) 732 4197
Michael Reimer, Founder of CRM Pros
Michael's takeFounder of CRM Pros · HighLevel Commander

The logs show the response. Start there.

Questions

Common questions.

Why is my webhook not firing?

Webhooks usually fail because the workflow is not published, the URL is wrong, an inbound webhook never received a sample payload to map, the method or authorization is wrong, or the receiving server rejected it, and the webhook logs show which one happened.

How do I prevent it?

Always send a test payload before mapping, send only the fields the other system uses and check the logs after launch.

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 action runs and the logs show no response at all, send support the workflow name, the action, the destination URL, the time of the run and a copy of the log entry. Remove any secret from what you send.

What is the difference between an inbound webhook and a custom webhook?

An Inbound Webhook is a workflow trigger that receives data from another app. A Custom Webhook is a workflow action that sends data to another system.

Why are the fields empty on my inbound webhook?

The incoming fields were not mapped. Send a test request so HighLevel sees a sample payload, then map each field to a contact field.

Do webhooks cost extra in HighLevel?

Inbound Webhook and Custom Webhook are premium workflow features and can carry a small charge per execution. Check the workflow premium settings in your account.

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
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.