Skip to content

Webhooks or Zapier for form submissions?

When to send form answers straight to your own system with a signed webhook, and when a tool like Zapier or Make is worth it.

2 min read

On this page

Once form answers need to reach another system, such as a CRM, a database or a spreadsheet, there are two common routes. You can send each submission straight to that system with a webhook, or hand it to an automation tool like Zapier or Make and let it do the rest. Both work. They suit different teams and different jobs.

What a webhook is

A webhook is a simple idea: when something happens, one system sends an HTTP request with the details to an address you choose. For forms, that means every submission arrives at your own endpoint as JSON, a second or two after the visitor presses send.

Formpik's Send webhook step posts a body like this:

{
  "event": "submission.created",
  "submission_id": "sub_8f2k1q",
  "form": { "id": "frm_31ad", "name": "Quote request" },
  "source": { "id": "src_77c0", "name": "Website", "domain": "example.com" },
  "received_at": "2026-11-02T10:24:51.000Z",
  "data": { "name": "Ada", "email": "ada@example.com", "budget": "5000" },
  "values": {}
}

Sign and check every delivery

Anyone who learns your webhook address could post fake submissions to it. That is why every Formpik delivery carries a signature header, X-Formpik-Signature: t=<seconds>,v1=<hex>, an HMAC SHA-256 of the timestamp and the raw body made with your destination's signing secret. Check it before you trust the body, and refuse old timestamps so a copied request cannot be replayed:

import { createHmac, timingSafeEqual } from 'node:crypto'

export const verify = (rawBody, header, secret) => {
  const parts = Object.fromEntries(header.split(',').map(part => part.split('=')))
  const age = Math.abs(Date.now() / 1000 - Number(parts.t))

  if (!parts.v1 || age > 300) return false

  const expected = createHmac('sha256', secret).update(`${parts.t}.${rawBody}`).digest()
  const given = Buffer.from(parts.v1, 'hex')

  return given.length === expected.length && timingSafeEqual(given, expected)
}

Always compute the signature over the raw body exactly as it arrived, before any JSON parsing changes it.

When a webhook is the better choice

  • You own the receiving system. Your app, your database, your backend. A webhook is direct, fast and costs nothing per task.
  • You need it to be reliable and checked. Signed deliveries, a 10 second timeout and the run history in Submissions show exactly what was sent and what came back.
  • You care about where data goes. One hop from Formpik to you, with no third service holding a copy.

When Zapier or Make is the better choice

  • The other app has no API you want to deal with. These tools have ready connections for thousands of apps.
  • Nobody on the team writes code. Mapping fields in a visual editor beats writing a receiver.
  • The job has many steps across other apps, such as adding a row to a sheet, creating a CRM deal and a calendar event.

You can combine both. Point a Formpik webhook at a catch hook address in Zapier or a custom webhook in Make, and let it take over from there. And the other way round: a Zap or a Make scenario can send data into Formpik with a webhook step, so answers from other apps get the same flows and inbox as your website forms.

Before you build either

Check what Formpik can do on its own. Email, replies to the sender, Slack, Teams, Discord, Google Chat, Mattermost and Telegram are steps in the flow, with routing, conditions and waits. Many teams never need a third tool at all.

References

Keep reading

More from the blog