Typeform Webhooks: Send Form Responses to Sazabi

Webhook facts checked on the platform’s docs on Nov 8, 2026.

A Typeform webhook sends each new response to a URL as soon as someone submits the form. Typeform still stores the response, so the webhook is a copy rather than a replacement. This page covers the payload and how to keep that copy in Sazabi.

What Typeform sends

The event is a new response submission. A payload has event_type set to form_response, and a webhook can also subscribe to form_response_partial to receive responses that were started but not finished. Every payload has an event_id and a form_response object.

Inside form_response you get form_id, token, submitted_at, landed_at, any hidden fields and variables, plus a definition of the form's fields and an answers array. Each answer has a type, a value under a key that matches the type, and a field object with the field id and type.

The payload carries the whole response. Nothing needs fetching afterward.

Why send it to Sazabi

A form is an entry point into your product: signups, support requests, survey answers. When submissions drop, someone has to know whether the form broke or people stopped using it. Sazabi's Webhook Events source stores each JSON payload as a searchable log record, with the payload under webhook.* attributes. Search for a respondent's email or a form ID, and the submission is next to the logs from whatever consumes it.

Use a path suffix per form, such as /typeform/signup. Sazabi stores it as webhook.path, so one intake URL can serve several forms without mixing them.

Set it up in Typeform

1. Open your form, go to the Connect panel and select the Webhooks tab.
2. Select Add a webhook.
3. Enter the Sazabi intake URL with a suffix as the Destination URL. The URL must start with https://.
4. Select Save webhook. The new webhook is Off, so switch the toggle on.
5. Select View deliveries, then Send test request. Test deliveries are marked Test, and the webhook must be On to redeliver one.
6. Select Edit to choose a trigger: completed responses only, or completed and partial responses.

Typeform stores deliveries for 30 days, and you can open the request and response for each. You can also manage webhooks with the Webhooks API, where PUT /forms/{form_id}/webhooks/{tag} creates or updates one.

Example payload

An abbreviated payload using field names from the Typeform docs. It is an example, not a captured delivery.

{
  "event_id": "LtWXD3crgy",
  "event_type": "form_response",
  "form_response": {
    "form_id": "lT4Z3j",
    "token": "a3a12ec67a1365927098a606107fac15",
    "submitted_at": "2018-01-18T18:17:02Z",
    "hidden": { "user_id": "abc123456" },
    "answers": [
      { "type": "email", "email": "laura@example.com", "field": { "id": "SMEUb7VJz92Q", "type": "email" } },
      { "type": "text", "text": "Laura", "field": { "id": "JwWggjAKtOkA", "type": "short_text" } }
    ]
  }
}

In a Sazabi thread, search for webhook.event_type to separate complete from partial responses. Responses hold whatever people typed, including personal details, so consider which forms you route here.

What to watch for

• Disabled webhooks. Typeform disables a webhook that fails 100 percent of the time within 24 hours with more than 300 delivery attempts, or within five minutes with 100 attempts, and notifies you. It also disables one immediately on a 404 or 410 response.
• Intake URL changes. If the Sazabi intake URL stops accepting events, for example after its public key is deleted, Typeform sees failures. Update the destination in Typeform when you generate a new URL.
• Timeouts. Typeform waits 30 seconds, then retries.
• Duplicates. Retries can repeat a response. event_id and the response token identify one.
• Partial responses. If you opt into partials, one respondent can produce several records. Use token to group them.
• Timing. Responses can reach the webhook a few seconds before they appear in Typeform's own database.

The Intake page in the Sazabi dashboard shows ingestion volume per source. Compare it with the response count in Typeform.

Retries

Typeform expects a 2XX status. A 404 or 410 means no retry and an immediate disable. A 429, 408, 503 or 423 is retried every two to three minutes for 10 hours. Any other failure is retried five times with back-off. The docs list intervals from five minutes to four hours.

Typeform signs payloads when you set a secret, in the Typeform-Signature header. If the same responses feed marketing site events, see Webflow, and for form-driven bot traffic see Telegram.