Facebook Lead Ads to GoHighLevel Webhook: Setup & Fix (2026)

Updated October 15, 2026 · Written by The Architect, CreatorOpsMatrix

1. Facebook Lead Ads to GoHighLevel via Webhook: What Actually Happens

Meta’s lead webhook does not deliver the full form. It sends a short notification with a lead ID, and your system then fetches the answers from Meta’s Graph API.

1. Create a Meta app and subscribe the Page to lead notifications.
2. Verify your callback URL when Meta sends its verification request.
3. On each notification, fetch the lead by its ID using a token with lead-retrieval permission.
4. Map the answers and send them to HighLevel with the v3 Upsert Contact call (section 5).

2. Why Facebook Lead Ads Do Not Reach GoHighLevel

A lead ad can submit successfully while the CRM receives nothing. The cause is usually the link between the Meta Page, lead permissions, the selected form and the CRM integration, not the campaign.

HighLevel’s own troubleshooting guide points to four checks before you replace anything:

Official steps: HighLevel’s Facebook Lead Ads integration guide.

3. Make Architecture and API v3 That Work in 2026

Make offers a Facebook Lead Ads integration with a New Lead trigger, a Get Lead Details action and a webhook-management action. You don’t need a Meta developer app for ordinary lead automation. See Make’s Facebook Lead Ads integration.

A Make Custom Webhook is not the same as Make’s Lead Ads trigger. Pasting a generic Make webhook URL into Ads Manager will not make Meta send lead events to it. Use Make’s own trigger for the no-code route, or build the developer route in section 8.

The flow: Meta Lead Ad → Make trigger → Get Lead Details → Router (optional) → HighLevel API v3 upsert.

Private Integration Tokens and v3

Older tutorials use the legacy API key or call the 2021-07-28 Contacts API “V2”. For a new build, HighLevel’s versioning documentation lists v3 as supported, with v3 Create and Upsert Contact at services.leadconnectorhq.com.

Private Integration Tokens can be created per agency or sub-account, are used as Bearer tokens and can be rotated in HighLevel. Give them only the scopes the workflow needs, and never put them in public code, screenshots or templates. References: Private Integrations · API Versioning

Why Upsert, not Create: retries and reconnects can run a workflow twice. HighLevel’s v3 Upsert Contact follows the location’s duplicate-contact settings, so a repeat run updates the contact instead of duplicating it.

4. Build the Make.com Workflow

Step 1: Connect Facebook Lead Ads

Create a scenario, pick the Facebook Lead Ads app and use the New Lead trigger. Select the Page and lead form, complete the permission flow, then send a real test lead and confirm the scenario receives it.

Step 2: Retrieve the lead details

Use Get Lead Details to read the submitted answers instead of assuming every lead arrives as a flat object. If the data contains arrays, use Make’s Iterator to process each item.

Step 3: Normalize the data

Build a clean mapping before the HighLevel call: first name, last name, email, phone, campaign or form ID, custom answers, lead source and optional owner or routing value.

Step 4: Create the HighLevel connection

In HighLevel, create a Private Integration with minimum scopes, copy the token and store it securely in Make. Send it as:

Authorization: Bearer YOUR_PRIVATE_INTEGRATION_TOKEN

Step 5: Send the lead to API v3

In Make’s HTTP module, POST to the v3 Upsert Contact endpoint:

POST https://services.leadconnectorhq.com/contacts/upsert

Authorization: Bearer YOUR_PRIVATE_INTEGRATION_TOKEN
Content-Type: application/json
Accept: application/json
Version: v3

{
  "firstName": "{{first_name}}",
  "lastName": "{{last_name}}",
  "email": "{{email}}",
  "phone": "{{phone}}",
  "locationId": "YOUR_LOCATION_ID",
  "source": "Meta Lead Ad",
  "customFields": [
    { "key": "monthly_ad_spend", "fieldValue": "{{monthly_ad_spend}}" },
    { "key": "business_type", "fieldValue": "{{business_type}}" }
  ]
}

The v3 Contacts documentation uses customFields objects with fieldValue. Don’t copy older examples that use field_value. Your Make variable names depend on what your Facebook connection returns, so treat this as an API-shape example.

Step 6: Read the response

The v3 Upsert response says whether a contact was created and returns the contact object and a trace ID. Log failed HTTP responses, because a successful trigger doesn’t mean the CRM call worked. Check each stage in order: Meta lead exists, Make received it, HighLevel accepted it, the CRM record is correct.

5. Mapping, Routing and Duplicates

If a form question changes wording, you update the mapping layer instead of rebuilding the CRM request.

Route leads to multiple sub-accounts

This is where Make beats point-to-point sync. A Router can read a campaign, form, ad set or geography value and send the lead to a different HighLevel location ID.

HighLevel’s contact API supports assignedTo when you already know the user ID. For complex ownership rules, send the contact to the right location and let HighLevel’s workflows assign the rep.

Prevent duplicate contacts

6. Troubleshooting and Current Rate Limits

HighLevel API rate limits

HighLevel documents a burst limit of 100 requests per 10 seconds and 200,000 requests per day, counted per Marketplace app and resource such as a Location or Company. Treat the response headers as the authority instead of a fixed sleep value:

X-RateLimit-Limit-Daily
X-RateLimit-Daily-Remaining
X-RateLimit-Interval-Milliseconds
X-RateLimit-Max
X-RateLimit-Remaining

For bulk migrations, control concurrency and retry failures. See the current rate-limit documentation.

7. Advanced Meta Webhook Setup

This route is for developers who want Meta’s Page webhook to call their own endpoint. It normally needs a Meta developer app, webhook verification, a leadgen subscription for the Page and the permissions required to retrieve lead data. It is different from adding Make’s Custom Webhook module.

Keep these stages separate so a failure is easy to locate: webhook delivery, lead-detail retrieval, normalization and validation, HighLevel delivery, error handling and replay.

8. Production Test Checklist

Don’t switch a live campaign from native sync to Make until each layer is verified.

9. What Make Costs in 2026

Make bills in credits. Its pricing page lists a Free plan with 1,000 credits per month and a Core plan at $12 per month for 10,000 credits. Usage depends on modules and processing, and arrays that create extra bundles consume extra credits, so don’t price this by module count alone. Check Make’s current pricing before you model production cost.

Frequently Asked Questions

Official Documentation Used for This Guide