Webhooks for form submissions

A webhook is an HTTP request Formboost sends to a URL you choose the moment a submission clears screening, with the submission as JSON. Email tells you a form was filled in; a webhook lets something happen — a CRM contact created, a row appended, a workflow started, your own code run.

• •Custom webhooks start on the Starter plan ($9/mo); Slack, Discord, Telegram and email delivery are on the free plan.
• •The URL must be public HTTPS. Choose the method (POST by default; GET, PUT and PATCH are accepted) and add any headers the receiver needs.
• •One attempt per submission with a 15-second timeout, logged with its status code. There is no automatic retry and no signature header — authenticate with a header you set.
• •eventId is stable per submission, so a consumer that sees the same event twice can drop the duplicate.

• •Your own backend — an API route or serverless function that writes to your database or sends a confirmation.
• •A CRM or SaaS API — HubSpot, Pipedrive or any endpoint that accepts JSON, authenticated with a header.
• •An automation platform — Zapier and n8n are first-class destinations with the same payload; Make and IFTTT are reachable through their webhook triggers.
• •A capture tool while you build — webhook.site shows the exact request before you write a line of code.

• •Open the form in your dashboard and go to Integrations → Webhook.
• •Paste the endpoint URL. It has to be reachable from the public internet over HTTPS — localhost and private addresses are refused.
• •Pick the HTTP method. POST is the default and what most receivers expect.
• •Add custom headers as needed — an Authorization: Bearer … or X-API-Key header is how you authenticate against an API. Host, Content-Length, Connection and Transfer-Encoding are ignored if set.
• •Save, then click Send test. The test carries event: form.submission.test and shows up in the delivery log like a real one.

Open webhook.site, copy the unique URL it gives you, paste it as the webhook URL and send a test. You will see the method, every header and the JSON body exactly as your real endpoint will receive them. The envelope itself — event, eventId, sentAt, form, submission — is documented in the contract above and is identical for Zapier and n8n.

Formboost waits up to 15 seconds for a 2xx and makes one attempt. Acknowledge first and do slow work afterwards:

// Express example
app.post("/hooks/formboost", (req, res) => {
  if (req.get("authorization") !== `Bearer ${process.env.FORMBOOST_HOOK_TOKEN}`) {
    return res.sendStatus(401);
  }
  res.sendStatus(200);            // acknowledge inside the timeout
  processSubmission(req.body);    // then do the real work asynchronously
});

A non-2xx or a timeout is recorded as a failed delivery with the status code in Integrations → Delivery log. Because there is no retry, fix the endpoint and use Send test to confirm before relying on it — the submission itself is always stored and visible in the dashboard regardless.

• •HTTP webhook setup reference
• •The form endpoint that produces the submission
• •All integrations