Webhook Subscriptions: Real-Time Submission Events
Receive every form submission on your own server in real time — HMAC-signed webhook payloads, retry behavior, and delivery guarantees explained.
What is the core specification for webhook subscriptions: real-time submission events?
Form2Lead dispatches HTTP POST payloads containing submission field JSON to your configured webhook URL immediately after receiving and validating a form submission — with automatic retries for failed deliveries.
Payload format
Each webhook delivery is a POST with Content-Type: application/json. The body contains the submission id, the form id, the timestamp, and every named form field as key-value pairs. Configure your endpoint URL in the form settings and Form2Lead streams every valid submission to it in real time.
Delivery guarantees
Webhook delivery is retried with backoff when your endpoint returns a non-2xx status or times out. This makes Form2Lead a reliable event source for Zapier, Make, Discord, Slack, or your own backend pipeline.
Webhook Subscriptions: Real-Time Submission Events FAQ
Can I send webhooks to multiple URLs?
Each form supports one webhook endpoint URL at a time. For fan-out, point Form2Lead at a middleware URL (for example Zapier or Pipedream) that forwards to multiple destinations.