Zapier

The BootForm app for Zapier starts a Zap the moment a form gets a new submission. You build the rest of the Zap out of any of Zapier's apps: a row in Google Sheets, a contact in your CRM, a message in Slack.

What you need

• A BootForm account on the Pro plan or higher.
• A BootForm API key: dashboard, Settings → API Keys. Zapier stores it once as a connection.
• A Zapier account.

What the app does

Part	What it does
New Submission trigger	Instant: BootForm sends each new submission to your Zap as it arrives. Submissions marked as spam are never sent.

That is the whole app: one trigger, with no actions or searches. A Zap can't change anything in BootForm. To star, archive or moderate a submission from an automation, use the API.

Set up the Zap

1. In Zapier, create a Zap, choose BootForm as the trigger app and New Submission as the event.
2. Account: connect BootForm by pasting your API key. The connection is labelled with the key's last four characters, so you can tell two connections apart.
3. Form: pick the form to watch from the list.
4. Test trigger: Zapier loads up to three of the form's latest submissions to use as samples. If the form has none yet, submit it once first.
5. Add the steps that should run for each submission, mapping the fields from the BootForm step.
6. Publish the Zap. This adds a zapier destination to the form in BootForm, which you'll see in the form's Workflow tab with its own delivery log.

Submit your form once more. The run shows up in the Zap's history.

Each Zap watches one form. To send several forms to the same place, make one Zap per form.

What the Zap receives

The same body as a webhook:

{
  "id": "9a2b3c4d-5e6f-7081-92a3-b4c5d6e7f809",
  "form_id": "11111111-1111-4111-8111-111111111111",
  "created_at": "2026-08-15T11:30:00Z",
  "fields": { "name": "Alice", "email": "alice@example.com", "message": "Hello there" },
  "files": []
}

created_at is when BootForm accepted the submission. Each entry in files has a name, size, mime and a url, and that link is only valid for 1 hour, so copy the file in the same Zap run if you want to keep it.

Turning it off

Turning the Zap off removes the zapier destination from the form again. Submissions are still stored in BootForm either way.

If Zapier refuses three submissions in a row with 410 Gone (nothing is listening on the hook), BootForm pauses the zapier destination and emails you once. To resume, turn the Zap on, then choose Enable in the destination's menu in the form's Workflow tab.

Troubleshooting

Symptom	Cause
The connection won't save	The API key is wrong or revoked
The Zap won't turn on, with a message that the account needs the Pro plan	Zapier and Make need the Pro plan or higher
Your form is missing from the Form list	The list shows the forms of the account the API key belongs to. Check you used a key from the right account
A spam submission didn't reach the Zap	That's by design: only submissions that aren't marked as spam are sent
The zapier destination shows Disabled and you got an email about it	Three submissions in a row were refused with 410. Turn the Zap on, then choose Enable in the destination's menu
A file link doesn't open	File links expire after 1 hour. Copy the file in the same Zap run

Prefer Make? See the Make guide. Want a plain HTTP request to your own server instead? See Webhook setup.