Send Facebook and Instagram lead ads to any webhook URL as JSON within seconds. Name your own field keys, sign requests with HMAC-SHA256, and plug into Make, n8n or your own app.
Setup
Three steps, and most people are live in about three minutes.
Sign in with Facebook and pick the Page you run lead ads on. We subscribe it to Meta's leadgen webhook, which is what makes delivery instant rather than scheduled.
Paste your https:// endpoint URL, and optionally a signing secret. There is no account to authorise. Rename any field to choose its JSON key, send a test lead to see exactly what your endpoint receives, then turn it on.
Each form question becomes a key in the JSON, named however your code expects. Send a test lead to see the exact request your endpoint gets, then switch it on.
What arrives
An HTTPS POST to your URL the moment a lead is submitted, with a JSON body: the event name, the Facebook lead ID, when it was submitted, a fields object holding each form answer under a key you name, and a source object with the Page, form, campaign and ad. With a signing secret set, each request also carries an X-LeadSender-Signature header (HMAC-SHA256 of the body).
Alongside the answers themselves, each lead carries the campaign and ad it came from, the Facebook Page name and the time it was submitted, inside a separate source object, so your code never has to tell a form answer apart from the metadata. Every attempt is recorded in Run history; when your endpoint rejects one, you see the HTTP status or error it gave, and you can resend that lead from there once it is fixed.
Who it suits
Developers and agencies wiring Facebook leads into their own app, a custom CRM or a database, and anyone already building workflows in Make, n8n or Pipedream who wants a reliable Facebook lead trigger without maintaining Meta tokens themselves.
This isn't an automation platform you have to learn. It handles the hard part, a working subscription to Meta's leadgen webhook, Page tokens that stay valid and a delivery log, then hands each lead to your endpoint as clean JSON so your own code or workflow can take it from there.
Use cases
About the tools
Facebook Lead Ads, now Meta lead ads, let people send you their details through an instant form on Facebook or Instagram without leaving the app. The form pre-fills from their profile, which is why these ads convert well and why the leads go cold fast if nobody follows up.
A webhook is an HTTPS address that accepts data the moment something happens. Developers, Make, n8n, Pipedream and most modern apps can receive one, which makes it the universal way to plug Facebook leads into a tool that has no dedicated integration.
LeadSender connects Facebook and Instagram lead ads to the tools you already use. It listens to Meta's leadgen webhook, maps each answer to a real field and delivers every lead in seconds, with a LeadScore quality check on the way. No Zapier, no CSV exports.
FAQ
Connect your Facebook Page in LeadSender, choose Webhook as the destination, paste your https:// endpoint URL and send a test lead. Once it is switched on, every new lead form submission is POSTed to that URL as JSON within seconds.
Within seconds. LeadSender is subscribed to Meta's leadgen webhook, so Facebook tells us the moment a form is submitted and we POST it straight on to your URL. There is no polling interval.
Each lead is a POST with a JSON body: event (lead.created), test (true only for test sends), lead_id, created_time, a fields object holding every form answer under the key you named, a source object with the Page, form, campaign and ad, and sent_at. The builder shows the exact JSON for your form before you turn it on.
Add a signing secret. Each request then carries an X-LeadSender-Signature header in the form sha256=<hex>, an HMAC-SHA256 of the raw request body using your secret. Compute the same HMAC on your side and compare before trusting the payload.
Yes. Paste the URL of a Make custom webhook, an n8n Webhook node or a Zapier Catch Hook and each lead arrives as a new run. LeadSender keeps the Facebook connection and Page tokens working, so the workflow only has to handle the lead.
The attempt is marked failed in Run history with the HTTP status or error your endpoint gave, for example a timeout after 10 seconds or a 500 response. Once your endpoint is back, resend that lead from Run history.
Any public https:// URL. Plain http, localhost and private network addresses are refused, and redirects are not followed, so point it at the final URL your endpoint answers on.
