What works today
Zapier's built-in "Webhooks by Zapier" action needs no lead2inbound-specific app: set your Zap's trigger to whatever produces the lead (a new Typeform response, a new row in a sheet, a CRM stage change), add a "Webhooks by Zapier → POST" action, point it at https://api.lead2inbound.com/v1/leads, set the Authorization header to Bearer YOUR_API_KEY, and map your trigger's fields to ours (phone is the only required one). That's a fully working step 1, lead in path right now, using our live HTTP POST endpoint underneath.
What's coming: a native app
A dedicated lead2inbound app in the Zapier directory is on the roadmap — pre-built triggers/actions, a guided field-mapping step, and no need to hand-construct the webhook body yourself. We evaluated Zapier as our primary Facebook Lead Ads path and rejected it for that specific job (it requires a paid Zapier plan, a per-tenant Zap to configure, and an extra hop that can silently fail vs. a direct 2-click Meta OAuth connection) — but as a general-purpose fallback across thousands of other tools, it's genuinely useful, which is why we're building the native app rather than leaving it as generic webhooks forever.
FAQ
Do I need to wait for the native app to use Zapier?
No. Zapier's generic Webhooks action already works against our live API today — the native app will make setup faster, not unlock new capability.
Can Zapier be my Facebook Lead Ads path?
It can work as a stopgap while our native Facebook integration clears Meta's review, but we don't recommend it long-term — it needs a paid Zapier tier and a Zap per lead form, versus a direct one-time OAuth connection.