Send Facebook Lead Ads leads to Juiced
Meta's own webhook only sends a lead ID, not the lead, so Facebook and Instagram instant form leads reach Juiced through a connector: Zapier, Make or GoHighLevel. This guide covers the Meta side and the trigger, then hands off to the shared POST step.
Route: via Zapier or Make (or GoHighLevel if you already use it). Trigger on Facebook Lead Ads > New Lead in Zapier or Watch Leads in Make, then POST JSON to Juiced.
You need admin-level access to the Facebook Page and its Business Manager, leads access assigned to your connector, a paid Zapier plan or a Make account, and a Juiced source with a bearer token.
The gotcha: leads access. If the Page's Leads Access settings do not include your connector, the trigger finds no leads even though the ads are running.
Before you start
- In Meta: a published instant form, and a Facebook account that can manage the Page and its ad account. Zapier lists the Manage Pages and Manage Ad Account permissions, and its Facebook Lead Ads (for Business Admins) version needs the Page in a business portfolio with full control access (Zapier: Facebook Lead Ads permissions).
- A connector: Zapier on a paid plan (Facebook Lead Ads is a premium app and Webhooks by Zapier is not on Free), or Make, or GoHighLevel.
- In Juiced: a source, its bearer token, and the field names from View API Spec.
Why not a direct webhook? Meta's lead webhook notification carries only leadgen_id, page_id, form_id and ad IDs; the answers have to be fetched separately with the Graph API (Meta: webhooks for leads). The connectors do that fetch for you.
Step by step
-
Create a source and copy a bearer token
In Juiced, go to Ingest > Sources > New source, turn on Test mode, click Create source, then create and copy a bearer token on the Authentication tab. Open View API Spec for the field names. Details: setting up a source.
-
Assign leads access to your connector
In Meta Business Settings, go to Integrations > Leads Access, click Assign CRMs, select your connector (Make, Zapier or LeadConnector for GoHighLevel) and click Assign (Make: Facebook Lead Ads). Zapier says this is needed when Lead Access has been customized. Ask the Page owner or a Business Manager admin if you cannot see the setting.
-
Connect Facebook Lead Ads in Zapier or Make
Zapier: add a Facebook Lead Ads connection and grant access in the Facebook window. Pick the standard version or Facebook Lead Ads (for Business Admins) to match how your access is set up (Zapier: Facebook Lead Ads). Make: add a Facebook Lead Ads module and click Create a connection; Make needs a Facebook account and a Business Manager account.
-
Choose the trigger, Page and form
In Zapier choose the New Lead trigger; in Make choose Watch Leads (if you use Make's New Lead trigger instead, Make says to follow it with Get Lead Details). Select the Page and the instant form. In Zapier, map the regular fields rather than the raw ones: Zapier recommends them because they are formatted consistently.
-
Add the POST to Juiced
Add the request that sends JSON to
https://usejuiced.com/api/v1/leadswith your bearer token, mapping each form field to a Juiced key (table below). Follow the Zapier POST step or the Make HTTP step. -
Create a test lead in Meta's testing tool
Open the Lead Ads Testing Tool, select the Page and form, click Preview Form and enter your own values with zip
00001, then submit. Click Track Status until it leaves pending. Only one test lead can exist per form, so click Delete Lead before creating another (Meta: testing lead ads). -
Check Incoming logs and go live
In Juiced, open Entries > Incoming logs, filter Test mode to Test only, and open the log to confirm every field arrived. Then publish the Zap or activate the scenario and turn off Test mode on the source.
Already on GoHighLevel? Connect the Page under Settings > Integrations, map form questions in Settings > Integrations > Facebook Form Field Mapping, then build a workflow with the Facebook Lead Form Submitted trigger and a Custom Webhook action to Juiced (HighLevel: Facebook lead ad integration). The webhook setup is in GoHighLevel to Juiced.
Field mapping
| Instant form question | Juiced key | Notes |
|---|---|---|
| First name, Last name | first_name, last_name | If the form asks for Full name, split it in Zapier or Make, or add a field for it. |
email | ||
| Phone number | phone | Check a test lead for the format Meta sends. |
| Zip code | zip | Always required. Add a zip question to the form. |
| Custom or qualifying question | Your custom key, e.g. home_owner | Each question appears as its own field in the trigger. Create the field in Juiced first; List of Values fields must receive a listed value. |
| Form ID, ad ID, campaign name | e.g. fb_form_id | Optional tracking fields; create them in Juiced to keep them. |
Form type, qualifying questions and any phone or email confirmation are set in Meta's form editor, not in Juiced. If an answer has to match a List of Values field, make the form's multiple choice options use the same wording.
TrustedForm and Jornaya
Instant forms run on Meta, so a TrustedForm or Jornaya script on your website never sees them. ActiveProspect issues TrustedForm certificates for Facebook lead ads only when leads come through LeadConduit's Facebook Lead Ads integration with TrustedForm added to the flow (ActiveProspect: TrustedForm for Facebook Lead Ads), so most sellers send Facebook leads without one. If you use that setup, map the certificate URL to a field such as trusted_form_cert_url. See passing TrustedForm and Jornaya certificates and LeadConduit to Juiced.
Troubleshooting
- The Page is missing from the dropdown. Your Facebook account lacks the needed permissions or uses the wrong Zapier version. Fix access, then reconnect the account in Zapier, which Zapier requires after any permission change.
- The trigger shows generic sample data. A new form with no submissions returns sample data. Create a test lead with the testing tool and test again.
- Test leads never arrive. Leads Access does not include your connector. For GoHighLevel, HighLevel says the testing tool should list LeadConnector's app; if it does not, reassign Leads Access.
- Can only create one test lead. Delete the existing test lead in the testing tool first.
- 422 with a zip error.
error.codeisvalidation_failedanderrorsnameszip. The form has no zip question, or the mapping points at the wrong field. - 401 Unauthorized. Check the bearer header has one space after
Bearerand no line break, and that the token was not replaced more than 24 hours ago.
More fixes: webhook troubleshooting.
Frequently asked
Can Facebook Lead Ads send leads straight to a webhook?
Not with the lead data. Meta’s lead webhook sends only the lead ID and related IDs, and the answers must be fetched with the Graph API. Zapier, Make and GoHighLevel do that fetch for you and can then post the lead to Juiced.
Which Zapier trigger do I use for Facebook leads?
Facebook Lead Ads, New Lead. Choose the Page and the instant form, and map the regular fields rather than the raw ones.
Why are my Facebook leads not reaching Zapier or Make?
Usually leads access. In Meta Business Settings, open Integrations, Leads Access and assign your connector as a CRM, then reconnect the account.
How do I test Facebook lead ads without running ads?
Use Meta’s Lead Ads Testing Tool. Select the Page and form, preview the form to enter your own values, create the lead and track its status. Only one test lead can exist per form.
Can I get a TrustedForm certificate for Facebook leads?
Only through ActiveProspect’s LeadConduit with its Facebook Lead Ads integration and TrustedForm in the flow. A TrustedForm script on your website does not see instant forms.
Sell every Facebook lead to the right buyer
Juiced routes each lead to buyers by their bids, caps and criteria, and unsold leads can go to your marketplace.
Scale your lead business, without limits
Juiced puts you in full control of your leads, routing, and revenue, so you can automate, optimize, and grow without chaos.