Help Center menu

Zapier & Make recipes

NodumForms' webhook can trigger any Zap or Make scenario directly — no native app required.

Quick setup in Zapier

  1. Create a new Zap.
  2. Pick Webhooks by Zapier as the trigger app, then Catch Hook.
  3. Zapier gives you a unique webhook URL — copy it.
  4. In NodumForms, open the form → Settings → paste the URL into Webhook URL → save.
  5. Submit one test response so Zapier can capture the payload schema.
  6. Add any action — Google Sheets row, Slack message, HubSpot contact, anything Zapier supports.

Quick setup in Make (Integromat)

  1. Create a new scenario.
  2. Add the Webhooks → Custom webhook module as the trigger.
  3. Click Add to generate a webhook URL; copy it.
  4. Paste it into the form's Webhook URL field.
  5. Submit a test response so Make can learn the schema.

Common recipes

New response → Google Sheets row Map each answer.value to a column. Useful for keeping a master spreadsheet of submissions.

New response → Slack message Format a friendly summary like "New {formTitle} submission from {answers[0].value}". Drop it in a #signups channel.

New response → CRM contact Push the email + name fields into HubSpot / Salesforce / Pipedrive as a new lead.

New response → custom backend Use webhook.site or your own endpoint to ingest responses directly into your product database.

Tips

  • Trigger one test submission with realistic data so Zapier/Make can infer field types correctly.
  • For lists (multi-select / file uploads), Zapier exposes them as arrays — most actions can join them into comma-separated strings if needed.
  • If submissions stop firing, check that the Zap is on and that your webhook URL hasn't expired (Zapier rotates URLs when you regenerate them).

Give feedback

Was this resource helpful?

|

Up next

Email notifications

Get an email every time someone submits your form — no webhook or integration required.

Read more

FAQs

A native Zapier app is on the roadmap. Today the easiest path is to point your form's Webhook URL at a Zap's "Catch Hook" trigger — every submission then fires the Zap with the full response payload.

No — webhooks are fire-and-forget. If your endpoint returns a non-2xx status, the response is still saved in NodumForms but the webhook is not retried. If reliability matters, point the webhook at a queue (Zapier, Make, or your own) that handles retries.

Not yet — a signing secret + signature header is on the roadmap. For now, treat the webhook endpoint as a trusted listener and protect it with a hard-to-guess URL path.