See the top GoHighLevel agencies in the USA for 2026: 14 ranked
How to connect Facebook Lead Ads to HighLevel, with or without a webhook
HighLevel connects to Facebook Lead Ads without a webhook. In the sub-account, go to Settings > Integrations, connect Facebook with an account that is Admin on both the Page and its Business Manager, pick the Pages, then map the form fields. A workflow with the Facebook Lead Form Submitted trigger then runs for each new lead. The webhook route (Meta, Zapier or Make into an Inbound Webhook trigger) is the alternative, and that trigger costs $0.01 a run after 100 free runs.
Updated
Facebook Lead Ads integration facts
| Fact | Detail | Source |
|---|---|---|
| Where to connect | Sub-account Settings > Integrations > Facebook (the Facebook–Instagram card) | help.gohighlevel.com |
| Meta roles needed | Admin on the Facebook Page and on the Business Manager it belongs to | help.gohighlevel.com |
| Lead sync choice | "All Leads" (past and new) or "New Leads Only" | help.gohighlevel.com |
| Pages per sub-account | Several Pages; HighLevel publishes no number limit | help.gohighlevel.com |
| Facebook accounts | Several per sub-account since November 4, 2026 (Labs switch); Shops and Ad Accounts still use one account | ideas.gohighlevel.com |
| Workflow trigger | Facebook Lead Form Submitted, filtered by "Page Is" and "Form Is" (one form per filter) | help.gohighlevel.com |
| Instagram leads | Included when the Instagram business account is linked to the connected Page | help.gohighlevel.com |
| Webhook route cost | Inbound Webhook is a premium trigger: 100 free lifetime runs per sub-account, then $0.01 per run | help.gohighlevel.com |
Step 1: connect Facebook in the sub-account
- In the sub-account, open Settings (bottom left), then Integrations.
- Click Connect on the Facebook–Instagram card and log in to Facebook.
- Approve the permissions HighLevel asks for, especially access to leads and Page data.
- Select the Page or Pages. On accounts with many Pages, search only works once every Page has loaded.
- Choose All Leads (past and new) or New Leads Only, then click Connect and Continue. A green "Integration successful" banner confirms it.
To change Pages later, open Integrations, then Facebook, choose "manage pages", tick the Pages and click update. Only the Facebook user who made the connection can choose its Pages (multi-page lead ads guide).
Permissions needed in Meta Business
- Page and Business Manager. HighLevel's 2026 connection guide requires Admin access to both the Page and the Business Manager it is connected to.
- Leads Access. HighLevel's lead ad guide (last modified 2023) says the connecting user needs lead access permission. Where a business uses Leads Access Manager, go to Business Settings > Integrations > Leads Access, click Assign CRMs, tick LeadConnector and click Assign.
- Keep the person. The same guide says the Page admin who granted permissions to LeadConnector must keep that access, or HighLevel can no longer fetch leads.
Step 2: map the form fields
Mapping decides which HighLevel contact field each lead form answer lands in. It sits under sub-account Settings > Integrations > Facebook Form Field Mapping. A blue tick next to a form shows it is mapped. Create any custom fields first, using a type the integration accepts: text, large text, numerical, phone, monetary, single options, date, dropdown, radio options or checkbox.
Campaigns built inside HighLevel follow the same rule. When Ad Manager shows that a form has unmapped fields, the lead ads setup guide says to use the mapping prompt. See GoHighLevel Ad Manager for building Meta lead campaigns from HighLevel itself.
Step 3: the Facebook Lead Form Submitted trigger
- Open Automation > Workflows and create or open a workflow.
- Click + Add New Trigger, scroll to the Events section and choose Facebook Lead Form Submitted.
- Set Page Is to the Page running the ad, then Form Is to the lead form.
- Save the trigger, add the follow-up actions, run Test Workflow and publish.
Without filters the trigger fires for every lead form on every connected Page, which HighLevel calls a common cause of unwanted runs. A Page only shows in the dropdown if it is connected under Integrations with the right permissions. A lead often ends in a team alert in the same workflow; see GoHighLevel internal notifications.
Several Facebook accounts per sub-account (November 4, 2026)
HighLevel's changelog moved the Facebook integration onto its Marketplace setup and allowed several Facebook accounts in one sub-account, each with several Pages. Lead sync, messages and automations work across Pages from different accounts. Existing connections move over without reconnecting. To use it, turn on "Facebook marketplace migration & multiple account support" in Labs, then go to Settings > Integrations, select Facebook and connect another account. Shops and Ad Accounts still support one Facebook account only. The change is logged in the GoHighLevel updates for November 2026.
The webhook route
| Route | How it connects | Which leads | Cost |
|---|---|---|---|
| Built-in Facebook integration | Settings > Integrations > Facebook, then the Facebook Lead Form Submitted trigger | Instant Forms on connected Pages; field mapping inside HighLevel | No premium charge stated in HighLevel's articles |
| Zapier | Facebook Lead Ads "New Lead" trigger to a LeadConnector action such as Add/Update Contact or Add Lead to Workflow | Leads Zapier can read on the Pages you authorise | Zapier's own plans |
| Make | Facebook Lead Ads "Watch Leads" or "New Lead" to the HighLevel "Create a Contact" module | Same, through Make's Facebook connection | Make's own plans |
| Meta webhook plus inbound webhook | A Meta app subscribed to the Page's leadgen field, a step that fetches the lead, then a POST to a HighLevel Inbound Webhook trigger | Any lead the app's token can read | Premium trigger runs, plus hosting the middle step |
Meta webhooks. A Meta app subscribed to a Page's lead events gets a leadgen notification with leadgen_id, page_id, form_id, ad_id, adgroup_id and created_time, but not the answers. The app reads those with a Graph API call on the leadgen_id. Meta's lead retrieval guide lists pages_manage_metadata for webhooks and leads_retrieval to read leads, and says notifications can arrive up to a few minutes late.
HighLevel's Inbound Webhook trigger. Adding it to a workflow creates a unique URL. It takes POST, GET or PUT requests, and the data must be a JSON object whose keys have no spaces. After saving a sample request, the Create Update contact action needs an email or phone field to create or update a contact (inbound webhook premium trigger guide). If the URL leaks, delete the trigger and add a new one. Inbound webhooks are a premium feature: 100 free lifetime runs per eligible sub-account, then $0.01 per run, with Workflow Pro plans getting included runs. The same premium billing covers the Google Sheets integration.
Zapier and Make do the fetching step for you. Zapier pairs the Facebook Lead Ads "New Lead" trigger with LeadConnector actions (Add/Update Contact, Add/Update Opportunity, Add Lead to Workflow, Stop All Workflows for Lead, Add Task). Make pairs "Watch Leads" or "New Lead" with HighLevel modules such as Create a Contact and Create an Opportunity. Either can also post to an Inbound Webhook URL.
Testing with Meta's Lead Ads Testing Tool
- Open Meta's Lead Ads Testing Tool at developers.facebook.com/tools/lead-ads-testing. It lists Pages the user has advertiser access to.
- Select the Page and the form, then click Create Lead. The lead holds dummy data unless Preview Form is used to type custom answers.
- Click Track Status until it shows success or failed. A failed row gives an
error_code. - Check the HighLevel sub-account for the new contact and the workflow run.
Meta allows one test lead per form; delete it to create another. Test leads are organic and not tied to any ad, so ad-level fields stay empty. HighLevel's 2023 guide says to look for LeadConnector's app (ID 39018126477806) in the tool; if it is missing, LeadConnector has no access to the Page's leads.
Limits
- One form per trigger filter setup.
- An Instagram account can be connected to only one Facebook Page.
- Only the Facebook user who connected a Page can see it in the Page dropdown.
- Shops and Ad Accounts support a single Facebook account, even after the November 2026 change.
- HighLevel publishes no limits on lead volume, forms or Pages.
To have lead routing like this set up, compare GoHighLevel CRM and automation agencies.
Frequently asked questions
How do I connect Facebook Lead Ads to HighLevel?
In the HighLevel sub-account, open Settings > Integrations and click Connect on the Facebook card. Log in to Facebook, approve the permissions, pick the Page and choose All Leads or New Leads Only. Then map the form fields and build a workflow with the Facebook Lead Form Submitted trigger.
What Facebook permissions does HighLevel need for lead ads?
HighLevel's May 2026 guide says the person connecting needs Admin access to the Facebook Page and to the Business Manager it belongs to. HighLevel's older 2023 lead ad guide adds that the person needs lead access and that, if Leads Access Manager is set up, LeadConnector must be assigned as a CRM under Business Settings > Integrations > Leads Access.
Can one HighLevel sub-account use several Facebook accounts?
Yes, since November 4, 2026, once the "Facebook marketplace migration & multiple account support" switch is on in Labs. Each account can bring several Pages for lead sync, messages and automations. Shops and Ad Accounts still work with only one Facebook account.
Can I send Facebook leads to a HighLevel inbound webhook?
Yes, through a middle step. Meta's leadgen webhook only sends IDs such as leadgen_id, page_id and form_id, so a tool such as Zapier, Make or custom code has to fetch the lead's answers from the Graph API and post them as JSON to the HighLevel Inbound Webhook trigger. That trigger is a premium feature billed per run.
How do I test Facebook lead ads with HighLevel without paying for ads?
Use Meta's Lead Ads Testing Tool at developers.facebook.com/tools/lead-ads-testing. Pick the Page and form, click Create Lead, then Track Status. The test lead is organic and not tied to an ad. Only one test lead can exist per form, so delete it before creating another.
Does one Facebook Lead Form Submitted trigger cover every form?
Only if it has no filters, in which case it fires for every lead form on every connected Page. Each filter setup covers one form. For several forms, HighLevel suggests cloning the trigger inside the same workflow with different filters, or using one workflow per form.
Sources
All checked November 11, 2026.
- HighLevel help: step-by-step guide to Facebook integration (last modified May 25, 2026)
- HighLevel help: Facebook multi-page lead ads integration (last modified May 25, 2026)
- HighLevel help: Facebook lead ad integration and troubleshooting guide (last modified September 15, 2023)
- HighLevel help: Facebook Lead Form Submitted trigger (last modified April 24, 2025)
- HighLevel help: set up Facebook and Instagram lead ads (last modified August 14, 2026)
- HighLevel changelog: Facebook Marketplace migration and multiple account support (November 4, 2026)
- HighLevel help: Inbound Webhook premium trigger (last modified September 16, 2026) and Inbound Webhook trigger (last modified April 8, 2025)
- HighLevel help: enable and rebill workflow premium features (last modified September 28, 2026)
- Meta for Developers: retrieving leads and lead ads testing and troubleshooting (undated)
- Zapier: Facebook Lead Ads and LeadConnector and Make: Facebook Lead Ads and HighLevel (undated)