How webhooks work
You give an app a URL, called the webhook endpoint. When an event happens, the app sends an HTTP POST request to that URL. The request body, usually JSON, describes the event. Your server reads the data and acts on it.
Example
A form gets a new submission. The form builder sends the answers to your server's webhook URL. Your server creates a contact in your CRM and posts a message to your team, in seconds and with no manual work.
Good practice
- Verify the signature on each request, so nobody can send fake events to your URL.
- Return a success response quickly, then do slow work in the background.
- Expect retries. If your server fails, the sender may send the same event again, so handle repeats safely.
Webhooks in FormFlux
FormFlux sends a webhook for each form submission. Each request has an HMAC-SHA256 signature in the X-Webhook-Signature header. Failed deliveries are retried up to 3 times with exponential backoff, and you can see the delivery logs. Webhooks are part of the Pro plan.