Webhook Integration

When the destination system is not one of LeadSync's native integrations -- internal company APIs, niche CRMs, low-code platforms (n8n, Pipedream, custom Lambdas), Slack incoming webhooks with custom payloads. If a dedicated integration exists for your destination, prefer it for the better field mapping and error handling.

POST, PUT, PATCH, GET, and DELETE. POST is the most common for creating records; PUT or PATCH for upsert patterns; GET for systems that accept lead data via query parameters.

Three built-in schemes: Bearer token (Authorization: Bearer header), Basic auth (Authorization: Basic header with base64-encoded user:pass), and API key in header (any custom header name like X-API-Key). For more complex auth like HMAC signing, put a thin proxy in front of your real endpoint.

You define it. Write the exact JSON structure your endpoint expects, with placeholder tags that LeadSync substitutes with each lead's values. This lets you match any API schema without writing a separate transformation layer.

Yes -- send leads to a Zapier or Make webhook trigger URL and the rest of your automation runs from there. That said, the dedicated LeadSync integrations for Mailchimp, HubSpot, and similar tools usually have better field mapping and faster delivery than going through Zapier as middleware, so prefer them when available.

LeadSync logs the error response (status code plus body) so you can diagnose. The lead is not retried automatically -- if your endpoint was temporarily down, you can manually re-process the lead from the LeadSync admin once your endpoint is back up.

Yes. The webhook destination is source-agnostic -- it works with lead forms from Facebook, Instagram, Google Ads lead form extensions, LinkedIn Lead Gen Forms, and TikTok Lead Generation. Each ad source becomes its own connection so you can route different platforms to different endpoints.

Not by default. If your endpoint requires a signed payload, the cleanest pattern is to add a Bearer token or API key in the auth configuration -- that gives your endpoint a way to verify the request is from LeadSync without per-payload HMAC. For HMAC-signed delivery specifically, use a thin proxy in front of your real endpoint that signs requests before forwarding.

LeadSync waits up to 30 seconds for your endpoint to respond before timing out and logging the failure. This is generous for most APIs but means you should not put long-running synchronous work behind your webhook -- accept the lead, return 200 OK quickly, and process asynchronously if needed.

Yes. Each LeadSync connection points at one endpoint, but you can create multiple connections for the same lead source -- one per destination URL -- and they will all fire in parallel for each new lead. Useful when you need to mirror leads to multiple internal systems or split delivery between primary and backup endpoints.