Webhooks
Alpha Feature — Webhooks are currently in alpha and available to early access users. Enable webhooks from Settings > Early Access to try them out. Functionality may change.
Webhooks let you send form submission data to external services (Zapier, Make, your own API, etc.) whenever a form is submitted.
Setting up a webhook
- Open a form in the builder
- Scroll down to the Webhooks section below the field list
- Click Add Webhook
- Enter the endpoint URL (must be HTTPS)
- Optionally add custom HTTP headers (e.g. an Authorization token)
- Click Save
You can add multiple webhooks per form. Each webhook fires independently.
Webhook payload
When a submission is created, each enabled webhook receives a POST request with the following JSON payload:
{
"event": "submission.created", "formId": "form_abc123", "submissionId": "sub_xyz789", "recordId": "attio-record-uuid", "data": { "email_addresses": "jane@example.com", "name": "Jane Smith", "company": "Acme Inc" }, "submittedAt": "2025-01-15T10:30:00.000Z" }
The data object contains all submitted field values keyed by their Attio attribute slug.
Managing webhooks
From the Webhooks section on the form editor:
- Enable/disable — toggle individual webhooks on or off without deleting them
- Edit — update the URL or headers
- Delete — permanently remove a webhook
Delivery behavior
- Webhooks are fired asynchronously after the submission is processed
- Each webhook has a 10-second timeout
- Webhook delivery does not block the submission response — if a webhook fails, the submission still succeeds
- Failed webhooks are not retried automatically
Use cases
- Send new leads to a Slack channel via Zapier
- Trigger a workflow in Make (Integromat) when a form is submitted
- Push submission data to your own backend API
- Sync form data to tools not natively connected to Attio