Glossary
What is Webhook?
How it works
You give the sending app a URL, the endpoint. When the event happens, the app sends a POST request to that URL with the details as JSON. The receiving side reads the data and acts on it: adds a row, creates a ticket, sends a message.
Good webhooks are signed, so the receiver can check they really came from the sender, and retried if the receiver is briefly unavailable, so no event is lost.
Example
A salon’s booking form sends a webhook to Make for every new response. Make adds the client’s details to a spreadsheet and posts a summary in the front desk’s chat, seconds after the form is submitted.
Tips
- Verify the signature on every delivery before trusting the data.
- Respond quickly with a success status and do slow work afterwards.
- Make your handler safe to run twice; retries can deliver the same event again.
- Use stable field references, not question wording, so edits don’t break your code.
Webhook in FormsAI
On FormsAI Pro, each new response is sent to your webhook endpoints as JSON, signed with an HMAC signature and retried automatically if delivery fails. Answers are keyed by references you set, so editing a question’s wording doesn’t break your integration. Pro also includes a REST API.
FAQ
Webhook, answered
What is the difference between a webhook and an API?
With an API, your code asks for data when it wants it. With a webhook, the other app sends data to your code as soon as something happens.
Do I need to code to use webhooks?
No. Paste a webhook URL from Zapier, Make or n8n and connect it to thousands of apps without code.