Integrations · Zapier · Lead Ads
Reliable Lead Ads intake into Bitrix24
Client:
Automotive marketplace, NDA
Category: Integrations
Stack: PHP 8.3, Bitrix24 D7, Zapier (Webhooks), JSON, business processes
Timeline: about 2 weeks
Problem
Leads from Facebook, Instagram and TikTok ad forms reached the CRM through Zapier's stock step: about 27 REST requests over OAuth per lead and roughly 10% of runs lost to timeouts — nginx logs showed the final request simply never reached the portal.
Constraints
Marketing owns the Zapier scenarios, and lead reports depend on the existing fields and author — the format had to stay simple for marketing, and the reports must not shift.
What I did
- A dedicated receiver: one POST with a static token instead of a chain of dozens of REST calls
- Idempotency by the social network's external_id: a Zapier retry does not create a duplicate but returns the same lead
- Raw request bodies are saved, plus a dry-run mode and a ping for the Zapier test step
- The lead is created with the same fields and author as before and triggers the same business processes
- A guide for marketing on switching scenarios, and 53 tests that run without Bitrix
Architecture
Lead Ads
→ Zapier: one POST
→ Token-protected receiver
→ Deduplication
→ Lead and business processes
Result
The receiver is ready and launches in September 2026: a lead arrives in a single request instead of a chain of ~27 calls, so the timeouts that ate about 10% of runs are ruled out by design.
What can be reused
Webhook receiver with a token and idempotency
Tolerant parsing of ad-form fields
Dry-run and ping for external integrators