Integrating with webhooks

Webhooks are NodumForms' primary developer-facing integration point today. Every form can fire a POST request to your endpoint on every submission, carrying the full response payload.

Setting up

1. Open the form → Settings → paste your endpoint URL into Webhook URL → save.
2. The webhook fires on every subsequent submission, asynchronously.

Payload shape

{
  "event": "response.created",
  "formId": "uuid",
  "formTitle": "Contact form",
  "responseId": "uuid",
  "submittedAt": "2026-05-31T14:23:11.000Z",
  "answers": [
    {
      "blockId": "uuid",
      "questionText": "Your name",
      "type": "SHORT_TEXT",
      "value": "Alex"
    }
  ]
}

For the complete reference and the full list of 13px] font-mono text-n-text">type values, see [Webhook payload reference.

Delivery guarantees

• At-most-once delivery — we send the request once. There's no automatic retry on failure.
• Asynchronous — the respondent's submission completes regardless of webhook outcome.
• Best-effort ordering — usually fires in submission order, not guaranteed under load.
• Timeout — we wait up to 10 seconds for your endpoint to respond before giving up.

What's not supported (yet)

• Signing / verification — no X-NodumForms-Signature header. On the roadmap.
• Multiple webhook URLs per form — one URL per form today. Fan out via Zapier or Make.
• Event filtering — every submission fires.
• Other event types — only response.created exists today.

Testing your endpoint

Point the webhook at webhook.site and submit a test response. You'll see the exact payload in real time.

Building a queue + retry layer

Because webhooks are fire-and-forget, production users typically pipe them through Zapier, Make, or their own queue (SQS, Pub/Sub, Cloud Tasks) and handle retries downstream. See Zapier & Make recipes.