← All guides

How to send one Meta webhook to multiple endpoints

2026-10-09

Facebook Lead Ads and the WhatsApp Business Cloud API both deliver webhooks to one callback URL per Meta app. There is no field in the App Dashboard for a second URL, and Meta's own documentation confirms that multiple endpoints require multiple Meta apps. If your CRM, your WhatsApp confirmation tool and an n8n flow all need the same lead, you have to choose one of four workarounds.

Option 1 — more Meta apps

Create one app per destination and subscribe each to the same Page or WABA. It works, but every app needs its own review, its own tokens, its own verify flow, and WhatsApp numbers can't be shared across apps freely. Most teams stop at two before this becomes the worst part of their week.

Option 2 — chain your tools

Point the webhook at tool A and have A forward to B. Now a bug or an outage in A silently stops B, you can't see what was dropped, and most SaaS tools don't forward at all.

Option 3 — Zapier / Make per event

Both can catch a lead and send it to several destinations, but you pay per task, retries are limited, and WhatsApp message webhooks (not just leads) aren't really their lane.

Option 4 — a fan-out relay

Put one endpoint in the Meta App Dashboard that verifies the X-Hub-Signature-256 header, answers the hub.challenge handshake, splits Meta's batched payloads, and re-delivers each event to every configured destination with retries, a log, and replay. Generic webhook routers can do pieces of this; the Meta-specific parts — signature verification, challenge, batch splitting, routing by Page / WABA / phone number id, re-signing each copy — are what you end up building yourself.