Dashform

Webhooks

Receive every completed reply as a signed HTTPS POST, verify it, deduplicate retries, and replay failed deliveries.

A Webhook integration POSTs each completed reply of a form to your own HTTPS endpoint as JSON. Add one from the form's Connect tab: choose Webhook, enter the endpoint URL and, optionally, a signing secret.

The endpoint must be a public HTTPS URL. Dashform follows up to five redirects, checking each hop the same way.

Request

Every delivery is a POST with these headers:

HeaderValue
Content-Typeapplication/json
Idempotency-KeyA hex string that identifies this delivery. Automatic retries and manual replays of the same delivery send the same key.
X-Dashform-Signaturesha256=<hex>, an HMAC-SHA256 of the raw request body keyed with your signing secret. Sent only when the integration has a signing secret.

By default the body is the JSON envelope:

{
  "schemaVersion": 1,
  "replyId": "5b8e1c2d-3f4a-4e6b-8c7d-9a0b1c2d3e4f",
  "formId": "0c2f7b0e-8d7e-4b8f-9a51-3f0d5e2a6c11",
  "formRevisionId": "9f1d2c3b-4a5e-4f6d-8b7c-1a2b3c4d5e6f",
  "formName": "Project discovery intake",
  "completedAt": "2026-11-16T18:04:12.000Z",
  "source": "web",
  "respondent": { "email": "ada@example.com", "name": "Ada Lovelace" },
  "fields": { "budget": "10k-25k", "timeline": "Q1" }
}
  • replyId is the reply's permanent id. It never changes, so use it as your primary key.
  • formRevisionId is the published revision of the form the respondent answered. Each publish creates a new revision, so two replies with the same formRevisionId were produced by the same questions and validation rules.
  • fields is keyed by each question's step key, not its label, so renaming a question does not rename its field.
  • A file-upload answer is the URL of the uploaded file.

New fields may be added to the envelope without changing schemaVersion. A change that removes or renames a field gets a new schemaVersion.

To send a different shape, switch Body format to Custom template and write the JSON yourself with tokens such as {{reply_id}}, {{form_revision_id}}, {{form_name}}, {{respondent_email}}, and {{answer:<step key>}}. Tokens go inside JSON strings.

Verifying the signature

Compute the HMAC over the raw body exactly as received, before parsing it, and compare in constant time:

import { createHmac, timingSafeEqual } from "node:crypto";

export const isFromDashform = (
  rawBody: string,
  header: string | null,
  secret: string
): boolean => {
  const expected = `sha256=${createHmac("sha256", secret).update(rawBody).digest("hex")}`;

  return (
    header !== null &&
    header.length === expected.length &&
    timingSafeEqual(Buffer.from(header), Buffer.from(expected))
  );
};

Responses, retries, and pausing

Answer with any 2xx status once you have stored the delivery. Dashform reads the status code:

Your endpoint answersWhat Dashform does
2xxMarks the delivery Delivered.
408, 429, 5xx, or no responseRetries after 1, 5, 15, and 30 minutes, five attempts in all, then marks it Failed. Ten failed deliveries in a row pause the integration.
401Marks it Failed without retrying.
Any other statusMarks it Failed and pauses the integration, since the endpoint looks gone or misconfigured.

Because retries reuse the Idempotency-Key, store the key or the replyId and ignore a delivery you have already processed.

Delivery log and replay

Open the integration on the form's Connect tab and choose View Delivery log. Each delivery shows its reply id, its state (Planned, Delivered, Failed, or Skipped), how many attempts it took, and the last error, including the status code your endpoint returned.

A failed or skipped delivery has a Replay button. Replay sends the same reply again with the same Idempotency-Key; the respondent does not resubmit anything. While an integration is paused its new deliveries are held, not dropped. Switch it back on from the same card to send them.

Testing a handoff

Point a second Webhook integration, or a copy of the form, at a test endpoint and submit the form yourself. Then delete the test reply from the Replies tab. Deleting a reply also deletes every file uploaded with it.

Exporting and deleting data

  • Export: the Replies tab exports CSV or JSON, and the listReplies API pages through every reply.
  • Delete: delete replies one at a time or in bulk from the Replies tab. Deleting a reply removes its answers and its uploaded files. Deleting a form removes all of its replies and their files, and deleting an organization removes everything in it.

These controls are the same on every plan, AppSumo tiers included.

On this page