Zapier

Zapier can start a Zap whenever a form is submitted, then pass the fields to any app it connects to: a CRM, a spreadsheet, a chat channel, a help desk. The connection is the SilentForms webhook pointed at a Zapier catch hook. No code is involved.

Webhooks by Zapier is a premium app, so it needs a paid Zapier plan. See Zapier's webhook trigger guide for which plans include it.

1. Create the trigger#

1. In Zapier, create a new Zap.
2. For the trigger, search for and choose Webhooks by Zapier.
3. Under Trigger event, choose Catch Hook and continue. Catch Hook parses the JSON body into separate fields, which is what you want here. Catch Raw Hook would give you the body as one string.
4. Continue to the Test tab. Zapier shows the webhook URL for this Zap. Copy it with the copy button next to it.

2. Set the webhook in SilentForms#

Sign in to the dashboard, open your form and save the Zapier URL as its webhook URL.

You could put the URL in a hidden webhookUrl field instead, but anyone viewing your page source could then send data into your Zap. Keeping it in the dashboard means only SilentForms knows it. The dashboard setting also overrides any webhookUrl field, so you can leave old forms unchanged.

3. Send a test submission#

Zapier learns the shape of the data from a real request, so it needs one before you can map fields.

1. Open your site and submit the form with realistic values. Fill in every field, including optional ones and at least one checkbox in each group, so all of them show up in Zapier.
2. Back in the Zap's Test tab, click Test trigger.
3. Zapier lists the request it caught. Open it and check the fields: name, email, message and anything else in your form, plus receivedAt.

If nothing shows up, check the submission in the dashboard. Its webhook status should be "sent", since Zapier answers with a 2xx status. "failed" or "error" means the URL is wrong or was mistyped.

4. Add an action and map fields#

Add the action step for the app you want, such as Google Sheets, Slack or Gmail, and connect your account. In each of the action's fields, click to insert data and pick values from the Catch Hook step: for example, put the trigger's email into a CRM's Email field and message into a note.

Things to know when mapping:

• Field names are your form's name attributes. If you rename a field in your HTML, the Zap keeps looking for the old one. Send a new test submission and re-map.
• Checkbox groups arrive as arrays, for example interests with ["Design", "Hosting"]. Check in the test data how Zapier presents them before mapping them into a single text field.
• receivedAt is an ISO 8601 timestamp in UTC, such as 2026-10-25T09:30:00.000Z. Zapier's Formatter app can convert it to your time zone if the destination needs local time.
• Special fields are not included. subject, from_name, redirect and the access key are used by SilentForms and removed before the webhook is sent. If you need a value in the Zap, send it as an ordinary field, such as a hidden source field.

Test the action step, then publish the Zap. From then on, every submission runs it.

Email, Zapier or both#

SilentForms emails you and calls the webhook for each submission. If Zapier should be the only destination, turn email notifications off in the dashboard for that form; every submission is still stored there.

If Zapier is down when a submission arrives, the delivery is retried after 1 minute, 5 minutes, 30 minutes, 2 hours and 12 hours. The submission in the dashboard shows how its delivery went and has a Retry now button if it gave up. See Webhooks for the details.

Spam#

Submissions caught by the honeypot are never sent to the webhook, so they do not use Zap runs. If a form attracts spam that gets past the honeypot, add a CAPTCHA such as Cloudflare Turnstile before it fills up your Zap history.

Next steps#

• Payload format and delivery rules: Webhooks.
• Prefer a different automation tool? Make or n8n.
• Write rows to a sheet without Zapier: Google Sheets.