How to connect GoHighLevel to n8n with webhooks (both directions)

By / Published Nov 16, 2026 / Updated Nov 16, 2026

Heads up: the trial and plan buttons on this page use my affiliate links. If you sign up through one I get a commission. It doesn't cost you more.

To connect GoHighLevel to n8n, add a Webhook or Custom Webhook action to a GoHighLevel workflow and paste in the URL from an n8n Webhook node, so every contact that reaches that step gets sent to n8n as JSON. To send data back, have n8n call HighLevel's API with a Private Integration token (or the official HighLevel node), or post to an Inbound Webhook trigger in a second GoHighLevel workflow.

That's the whole loop, and it's the part most tutorials stop short of. Below is the full build: the outbound step and what's actually in the payload, a secret header so randoms can't hit your n8n URL, the three ways back in and which scopes to tick, a complete new lead example where n8n scores the lead with AI and tags it in GoHighLevel, then testing, retries and what it costs on both sides (checked Nov 16, 2026). If you're still deciding which tool should run the automation in the first place, read vs n8n, Make, Zapier first.

Start your 30-day free trial →

30 days free instead of HighLevel's usual 14, plus a 1:1 setup call with my team, weekly live calls and my agency resources from day one. See everything you get →

Short version

  • 01Out: GoHighLevel workflow > Webhook (simple) or Custom Webhook (headers, auth, raw JSON) > n8n Webhook node's Production URL.
  • 02Publish the n8n workflow and use the Production URL. The Test URL only listens for 120 seconds after you click Listen for test event.
  • 03The payload only carries opportunity, appointment or invoice data if the workflow's trigger is about that object. A tag trigger sends contact data only.
  • 04Back in: HighLevel API v2 with a Private Integration token (most control), the n8n HighLevel node (contacts, opportunities, tasks, booking), or an Inbound Webhook trigger (no token, premium).
  • 05Custom Webhook and Inbound Webhook are premium: 100 free per sub-account for life, then $0.01 each, or Workflow Pro from $10 a month for 10,000 (Nov 16, 2026). API calls from n8n aren't workflow executions.
  • 06HighLevel doesn't document retries for workflow webhooks, so have n8n reply fast and do its own retries and error alerts.

The 10-minute round trip, in order

  1. 01

    Create the n8n Webhook node

    New workflow in n8n, add a Webhook node, set HTTP Method to POST, set Authentication to Header Auth (more on that below) and Respond to Immediately. Copy the Test URL for now.

  2. 02

    Add the outbound step in GoHighLevel

    Automation > Workflows, open or create a workflow with a trigger (Form Submitted, Contact Tag, whatever starts the job). Click +, then Send Data > Custom Webhook. Event CUSTOM, Method POST, paste the URL, add your secret header and a JSON body.

  3. 03

    Send one test

    In n8n click Listen for test event, then in GoHighLevel click Test Workflow and run it for a test contact. The data shows up in the Webhook node within the 120 seconds n8n listens.

  4. 04

    Build the logic and the way back

    Add your n8n steps, then write back with an HTTP Request to HighLevel's API (Private Integration token), the HighLevel node, or a POST to an Inbound Webhook URL.

  5. 05

    Switch to production

    Publish the n8n workflow, swap the GoHighLevel step to the Production URL, publish the GoHighLevel workflow, and run one real form submission end to end.

The four ways GoHighLevel and n8n talk to each other

There's no HighLevel trigger node in n8n, so anything that starts in GoHighLevel has to be pushed out by a workflow step. Coming back in, you have three options. Pick by how much control you need and how often it runs.

RouteDirectionUse it forGoHighLevel cost
Webhook actionGHL to n8nQuick sends: contact data plus a few custom keys, POST by defaultNot named in HighLevel's premium list
Custom Webhook actionGHL to n8nYour own JSON body, headers, auth (Bearer, API key, Basic, OAuth2)Premium execution
HighLevel API v2 (HTTP Request or HighLevel node)n8n to GHLUpdate the exact contact, add tags, set custom fields, create opportunitiesNot a workflow execution. Rate limited
Inbound Webhook triggern8n to GHLStart a GoHighLevel workflow with n8n's data, no token neededPremium execution

From HighLevel's help docs and API reference and n8n's docs, read Nov 16, 2026.

Step 1: send data out with Webhook or Custom Webhook

HighLevel has two outbound actions and their own doc tells you when to use which: Custom Webhook when you need auth and a request you build yourself, the plain Webhook for simpler sends.

The plain Webhook action: search "webhook" in the actions panel, leave Method on POST, paste the n8n URL. Under Custom Data, click + Add item to add keys like lead_source with a value or a custom value such as {{contact.source}}. Keys can't have spaces. It sends the contact's standard and custom fields and the sub-account's location details on every run.

The Custom Webhook action (+ Add action > Send Data > Custom Webhook) is the one I'd use for n8n. Set Event to CUSTOM to get the Method picker, Content-Type and a Raw Body editor. Then you send exactly the fields your n8n flow needs and nothing else, with the tag icon next to each field to insert values like {{contact.id}}. Event POST gives you key/value pairs only, and GET has no body at all.

Always send the contact ID. It's the one value that lets n8n update the right record later without guessing by email or phone.

  • A body for a new lead: {"contact_id": "{{contact.id}}", "first_name": "{{contact.first_name}}", "email": "{{contact.email}}", "phone": "{{contact.phone}}", "company": "{{contact.company_name}}", "source": "{{contact.source}}"}
  • Content-Type: application/json, Method POST.
  • Files and images can't go through the Webhook action. Send a link to the file instead.

What's in the payload (and why opportunity data goes missing)

This is the thing people get stuck on, going by the Reddit threads asking how to pull data out of a webhook. Every webhook carries the contact (name, email, phone, address, tags, every custom field) and the location object. Opportunity, appointment, invoice, task, note and message data only come along when the workflow's trigger is about that object.

So if you want the opportunity name, stage and value in n8n, the workflow has to start from an opportunity trigger like Pipeline Stage Changed. If you want the appointment time, start from Appointment Booked. A Contact Tag trigger will only ever send contact fields, however you set up the webhook. HighLevel's doc says it plainly: you must use the correct trigger to get the data you need.

One more catch: Execution Logs in GoHighLevel show the webhook step as Executed, but they don't show what was sent. To see the real payload, look at the n8n execution, or point the step at a webhook.site URL for one test.

Lock the n8n URL with a secret header

An n8n Webhook node with Authentication set to None will run for anyone who finds the URL. Fix that in two minutes.

In n8n, set the Webhook node's Authentication to Header Auth and create a credential with a header name like X-Webhook-Secret and a long random value. In the GoHighLevel Custom Webhook, set Authorization to No auth and add the same header under Headers, or pick API key and store it as a masked key. Custom Webhook masks Basic, Bearer and API key secrets, names them, keeps them inside that sub-account, and only agency admins or the person who made a key can delete it.

Keep secrets in headers, never in the URL. A key in a query string ends up in logs and screenshots. And don't plan on IP allowlisting: HighLevel says it can't give you a static IP for webhooks, so header auth is the way.

The same goes the other way. Your Private Integration token lives in an n8n credential, never pasted into a node's URL or a Code node, and never in a JSON export you share. n8n workflow files are handed around all the time, and a token in one is a token anyone can use.

Test URL vs Production URL: the mistake that breaks it the next day

Every n8n Webhook node has two URLs. The Test URL only works after you click Listen for test event (or Execute workflow), it listens for 120 seconds, and the data shows up right in the editor. The Production URL only works once the n8n workflow is published, and its runs show in the Executions tab, not on the canvas.

The classic bug: you test with the Test URL, it works, you publish the GoHighLevel workflow, and the next morning nothing reaches n8n. Swap the GoHighLevel step to the Production URL and publish the n8n workflow. Also, n8n only allows one webhook per path and method, so duplicating a workflow without changing the path will clash.

Step 2: get the result back into GoHighLevel

In my own round trip build (I used Make for it, same idea), the thing I called out was matching the record on the way back: "from the web hook you want to recognize who you want to send this information back to I put the phone number there as well just to match it perfectly." With n8n you can do better than matching on phone: send the contact ID out and use it on the way back.

Option A, HighLevel API v2 with a Private Integration token. In the sub-account go to Settings > Private Integrations > Create New Integration, name it, and tick only the scopes you need. For the build below that's contacts.readonly, contacts.write, opportunities.readonly, opportunities.write and locations/customFields.readonly (to look up custom field IDs). Copy the token straight away, it may only be shown once. In n8n, use an HTTP Request node with a Header Auth credential: Authorization set to Bearer plus the token, and add a Version header of 2021-07-28 to every call. Base URL is https://services.leadconnectorhq.com.

Option B, the n8n HighLevel node. It covers contacts (create or update, get, update, delete), opportunities, tasks, booking an appointment and getting free slots. The catch is setup: the API key option uses API v1, which HighLevel ended support for on December 31, 2025, so new credentials need OAuth2, which means creating an app in HighLevel's developer marketplace (Distribution Type: Sub-Account), adding the scopes and pasting n8n's redirect URL. Worth it if you connect many sub-accounts. For one client, the token in Option A is quicker.

Option C, an Inbound Webhook trigger. Make a second GoHighLevel workflow with the Inbound Webhook trigger, copy its URL, and have n8n POST JSON to it. No token, and the client can see and edit everything that happens after in the workflow builder. It's a premium trigger though, so every call costs an execution. Setup details are in the next section.

  • Add a tag: POST /contacts/{contactId}/tags with {"tags": ["hot-lead"]}
  • Set a custom field: PUT /contacts/{contactId} with {"customFields": [{"id": "FIELD_ID", "field_value": "8"}]}
  • Create an opportunity: POST /opportunities/ with pipelineId, locationId, name, status and contactId
  • Create or update by email or phone: POST /contacts/upsert (it follows the sub-account's duplicate contact setting)

Setting up the Inbound Webhook trigger and its mapping reference

Automation > Workflows > Create Workflow, add the Inbound Webhook trigger, and copy the URL it generates (each trigger gets its own). Have n8n send one real request to it, then click Test Trigger, and pick that request as the Mapping Reference. The newest one is at the top, and you can search by the ID in the response if there are a few. Save the trigger.

HighLevel then drops you into a Create Update Contact action to map the incoming fields. It needs an email or a phone to find or create the contact. If your payload has neither (say, an order or a daily report), delete that action and the workflow runs without a contact, which works for Slack, Google Sheets, Custom Webhook and If/Else steps.

Rules from HighLevel's doc: send JSON only, use keys without spaces (camelCase or snake_case), and if you change the shape of what n8n sends, go back and re-select the Mapping Reference or later steps won't see the new fields. If the URL ever leaks, delete the trigger and add a new one to get a fresh URL. The same trigger handles website forms, which is covered in Connect GHL to any website.

Full example: new lead, AI score in n8n, back to GoHighLevel

Here's a build you could set up for a local business and charge a monthly fee you set. A lead fills in the website form, n8n reads their message and scores how ready they are, and hot leads get tagged so the GoHighLevel side texts them and alerts the owner straight away.

In GoHighLevel, workflow 1 (Lead out): trigger Form Submitted, filtered to the quote form. Action Custom Webhook, Event CUSTOM, POST to the n8n Production URL, header X-Webhook-Secret, body with contact_id, first_name, email, phone, company and the form's message field.

In n8n: Webhook node (Header Auth, Respond Immediately, so GoHighLevel gets its 200 straight away). Then an AI step (the AI Agent or an OpenAI or Anthropic node) with a short prompt: score this lead 1 to 10 for how ready they are to book, return JSON with score and reason. An IF node splits on score of 7 or more. Both branches write the score to a custom field with PUT /contacts/{contactId}. The hot branch also adds the tag hot-lead with POST /contacts/{contactId}/tags and creates an opportunity in the right pipeline stage.

Back in GoHighLevel, workflow 2 (Hot lead): trigger Contact Tag added, hot-lead. Send the lead a text, send the owner an internal notification with the AI's reason, and start the follow-up sequence. Because n8n came back through the API and a normal tag trigger, nothing on the return trip is a premium execution. That's why I'd pick the tag route over an Inbound Webhook here.

Clean the AI's output before you write it anywhere. When I built my round trip with DeepSeek, the model put its thinking into the reply, and as I said in the video, "I basically spend all night coming up with a way to just extract only the output." Ask the model for strict JSON, then parse it in n8n before the HTTP Request runs. Don't let raw model text land in a customer's SMS.

Start the 30-day trial and build the GoHighLevel side →

How to test it without texting real leads

Test the outbound step against n8n's Test URL first, using GoHighLevel's Test Workflow on a contact that's you. Then open the n8n execution and check the JSON has every key you expected. If a value is blank, the custom value didn't resolve for that contact, or the trigger doesn't carry that object.

For the way back, run each HTTP Request node on its own in n8n and confirm the tag or field appears on your test contact. Then publish both sides, switch to the Production URL and submit the real form once. Check three places: the GoHighLevel workflow's Execution Logs, n8n's Executions tab and the contact record.

If GoHighLevel shows the webhook step failed, read the status code. 401 or 403 means the secret header doesn't match. 404 means the URL is wrong or the n8n workflow isn't published. Anything 5xx is n8n erroring before it replied. If the step ran but the workflow after it misbehaves, the checklist in Workflow not triggering covers the rest.

Error handling, retries and duplicates

HighLevel documents automatic retries for Marketplace app webhooks (429 responses, up to six tries about 10 minutes apart), but that doc says it's for Marketplace apps, and I couldn't find any retry policy for the workflow Webhook or Custom Webhook action as of Nov 16, 2026. So build as if GoHighLevel sends once. That puts the reliability on the n8n side.

  • Reply fast. Set the Webhook node to Respond Immediately. n8n Cloud sits behind Cloudflare, and a webhook that hasn't answered in 100 seconds fails with a 524. AI steps can be slow, so let them run after the reply.
  • Retry the calls back into HighLevel. Turn on Retry On Fail in the HTTP Request node's settings, and keep calls under HighLevel's API limit of 100 requests per 10 seconds per sub-account (200,000 a day). A 429 means slow down.
  • Catch failures. Set an error workflow in the n8n workflow's settings, starting with an Error Trigger, that messages you on Slack or email. Use On Error > Continue (using error output) on steps where you'd rather log and carry on.
  • Make writes safe to repeat. Adding a tag twice or setting the same field value twice does no harm. Creating an opportunity twice does, so search for one first or use the upsert endpoint.
  • Turn on GoHighLevel's workflow error notifications so a broken webhook step emails an admin.

What it costs on both sides (checked Nov 16, 2026)

GoHighLevel: Custom Webhook and Inbound Webhook are premium workflow features. Each sub-account gets 100 free premium executions for life, then it's $0.01 each. Workflow Pro bundles them per sub-account: Starter $10 a month for 10,000, Growth $25 for 30,000, Scale $50 for 65,000, with cheaper overage on each. You buy it inside the sub-account under Automation > Global Workflow Settings, and agencies can rebill the usage to clients with a markup. The plain Webhook action isn't named in HighLevel's premium list. API calls from n8n aren't workflow executions at all.

n8n: Cloud bills per workflow execution with unlimited steps. Starter is $20 a month billed yearly ($24 monthly) for 2,500 executions, Pro is $50 billed yearly ($60 monthly) for 10,000. The Community Edition is free to self-host, and you pay for the server. Your AI model usage for the scoring step is billed by whoever runs the model.

So the example above at 1,000 leads a month: 1,000 Custom Webhook runs in GoHighLevel (about $9 after the free 100, or the $10 Starter tier), and 1,000 n8n executions (inside n8n Starter). The bigger cost-at-volume comparison between GoHighLevel, n8n, Zapier and Make is on vs n8n, Make, Zapier.

ItemPriceNotes
GoHighLevel premium execution$0.01 each after 100 freePer sub-account. The 100 never reset
Workflow Pro Starter$10/month10,000 executions, then $0.008 each
Workflow Pro Growth$25/month30,000 executions, then $0.006 each
Workflow Pro Scale$50/month65,000 executions, then $0.004 each
n8n Starter (Cloud)$20/month yearly, $24 monthly2,500 executions, 5 at once
n8n Pro (Cloud)$50/month yearly, $60 monthly10,000 executions
n8n Community EditionFreeSelf-hosted on your own server

From HighLevel's Workflow Premium Features doc (mod. Sep 28, 2026) and n8n.io/pricing, read Nov 16, 2026. Plan prices exclude tax. AI model, messaging and hosting costs not included.

When you don't need n8n at all

A lot of GoHighLevel to n8n builds I see are steps GoHighLevel already does: send a text, add a tag, move a pipeline stage. Keep those in GoHighLevel, where the client can see them and there's nothing extra to host. Its workflow AI Builder can draft them from a sentence now, and the full builder walkthrough is in GoHighLevel workflows.

Reach for n8n when the job is data work GoHighLevel's builder isn't good at: calling an enrichment API, looping over a list, reshaping messy JSON, or chaining several outside apps. That's where my own round trip earned its place: the webhook goes out, the AI does its thing, and only the clean answer comes back. If you'd rather let an AI read and change the account directly, look at HighLevel's MCP in Connect Claude to GoHighLevel.

Start your 30-day free trial →

30 days free instead of HighLevel's usual 14, plus a 1:1 setup call with my team, weekly live calls and my agency resources from day one. See everything you get →

Other ways to start

My bonuses come with every one of these.

Best if you're new and want live help setting up

30-day trial + a free live setup bootcamp

Best if you're not sure which plan you need

Compare all 3 plans first

Best if you'll resell HighLevel as your own software

Go straight to the $497 Founder plan

FAQ

How do I connect GoHighLevel to n8n?

Add a Webhook or Custom Webhook action to a GoHighLevel workflow and paste the Production URL of an n8n Webhook node. To write back, call HighLevel's API from n8n with a Private Integration token, use the HighLevel node, or post to an Inbound Webhook trigger.

Does n8n have a GoHighLevel trigger?

No. n8n's HighLevel node only has actions (contacts, opportunities, tasks, booking and free slots). Events have to be pushed from a GoHighLevel workflow with a Webhook or Custom Webhook action to an n8n Webhook node.

What's the difference between Webhook and Custom Webhook in GoHighLevel?

Webhook sends the contact and trigger data plus any custom key/value pairs, POST by default. Custom Webhook lets you pick the method, headers, auth (Bearer, API key, Basic, OAuth2) and write your own JSON body. Custom Webhook is a premium action.

Why is my GoHighLevel webhook not reaching n8n?

Usually the step still points at n8n's Test URL, which only listens for 120 seconds, or the n8n workflow isn't published. Use the Production URL, publish both workflows, and check the status code in GoHighLevel's Execution Logs.

Why is opportunity or appointment data missing from the webhook?

The payload only includes those objects when the workflow's trigger is about them, like Pipeline Stage Changed or Appointment Booked. A tag or form trigger sends contact and location data only.

Do GoHighLevel webhooks cost extra?

Custom Webhook and Inbound Webhook are premium: 100 free per sub-account for life, then $0.01 each, or Workflow Pro from $10 a month for 10,000 (as of Nov 16, 2026). API calls from n8n into HighLevel aren't workflow executions.

Which scopes does the Private Integration token need for n8n?

Only what your flow touches. To update contacts and tags: contacts.readonly and contacts.write. For opportunities add opportunities.readonly and opportunities.write, and locations/customFields.readonly to look up custom field IDs.

Sources / last checked Nov 16, 2026

  • HighLevel help docs: webhooks. Workflow Action - Custom webhook (modified Dec 11, 2025), Workflow Action - Webhook (Outbound) (Mar 16, 2026), Workflow Trigger - Inbound Webhook (Apr 8, 2025), How to use the Inbound Webhook Workflow Premium Trigger (Sep 16, 2026), secure credentials in Custom Webhook (Apr 14, 2025), Webhook.site testing (Feb 4, 2026) and Marketplace Automated Webhook Retries (Jul 10, 2026), read Nov 16, 2026.
  • HighLevel help docs: pricing and tokens. Workflow Premium Features (Sep 28, 2026), Workflows Pro Plan - New Pricing Tiers (Sep 4, 2025) and Private Integrations (Nov 16, 2026), plus gohighlevel.com/pricing, read Nov 16, 2026.
  • HighLevel API v2 reference. Contacts, Opportunities and Locations API specs (tags, update contact, upsert, custom fields, create opportunity, Version 2021-07-28) and the marketplace API FAQ for rate limits, read Nov 16, 2026.
  • n8n docs and pricing. docs.n8n.io HighLevel node, HighLevel credentials, Webhook node, Webhook common issues, Respond to Webhook, node settings and error workflows, and n8n.io/pricing (both billing toggles), read Nov 16, 2026.
  • My video. "How to Integrate DEEPSEEK with GoHighLevel (Full Tutorial)" (Feb 2025), a GoHighLevel webhook round trip built with Make, quoted only and not embedded. I don't have a dedicated n8n webhook video, so there's no video on this page.
Hamza Baig (Hamza Automates)

Author

Hamza Baig / Hamza Automates

Founder, Hexona Systems

I run Hexona Systems on GoHighLevel. HighLevel gave it the SaaSpreneur Platinum award in 2024 and Diamond in 2025 and 2026, and I spoke at their LevelUp event in 2026. Hexona powers 1,000+ agencies, we've served 1,500+ businesses, and I've taught 45,000+ students. Everything on this hub is something I use myself or have shown on camera.

Platinum SaaSpreneur
2024
Diamond SaaSpreneur
2025, 2026
LevelUp speaker
2026
YouTube subscribers, Oct 2026
34,200

Keep reading

Start your 30-day free trial →

30 days free + 1:1 setup call + my bonus / affiliate link