Using Webhooks

Webhooks let you subscribe a URL of your own to events happening on a project, so tools like Zapier, Make, or your own backend can react automatically — without you needing to poll our API.

Tip

To send responses to a common app such as Slack, Google Sheets, Mailchimp or HubSpot, Actions do it directly — no webhook and no automation tool required. Use a webhook when you need to reach your own endpoint.

How to set up a webhook

1. Go to the Send section of your project.
2. Open the Developers tab, find Webhooks, and click Configure webhooks.
3. Click Add Webhook.
4. Fill out:
   • Name — a label to help you identify this webhook later.
   • Webhook URI — the URL we’ll send the payload to.
   • Authentication (optional) — enable HMAC signature and/or Authorization header if your endpoint needs to verify the request came from us.
   • Subscribed Events — choose one or more of the events below.
   • Active — toggle this off to temporarily pause the webhook without deleting it.
5. Click Add.

Your new webhook appears in the shared account list with Test, Edit, and Delete controls. Return to the form’s Webhooks panel and tick its checkbox under Select the webhooks this form should send to.

Subscribed events

Event	Fires when…
New Form Response	A respondent submits a response to this project.
Add/Update CRM Contact	A contact linked to this project is created or updated in your CRM.
Unsubscribe Contact	A contact linked to this project unsubscribes.

Webhooks are configured once for your account. To use the same webhook on another project, select that existing webhook in the other project’s Send → Developers → Webhooks panel. See Create and manage webhooks.