Do I need to use the webhook instead?

The Zapier connection is native. Pick FormWire's new-submission trigger in your Zap and you're done, with no webhook to wire up. The webhook stays available if you'd rather drive custom code directly.

Which fields are available in the Zap?

Your form's submission fields come through mapped and named (name, email, message and any custom fields you collect), so you can route each one to the right app without touching raw payloads.

Does spam trigger my Zaps?

No. Submissions are filtered for spam before anything fires, so your Zaps run on real leads and don't spend task quota on bots.

What happens if a Zap fails?

Nothing is lost. Every submission is stored and emailed before Zapier is notified, so the record stays in your dashboard whatever happens downstream, and you can re-run the Zap from Zapier's task history.

My Zap isn't firing on new submissions. What should I check?

First confirm the Zap is turned on. A Zap left in draft won't run. Then check the connected FormWire account is still authorized and pointed at the right form, and that the submission actually passed spam filtering, since filtered ones don't trigger. Your Zap's task history shows exactly what arrived.

Can I run multiple Zaps from one form?

Yes. A single form can trigger as many Zaps as you like: copy leads to a CRM, log a row in a sheet and ping a channel, all from the same submission.

Zapier integration

Trigger Zaps on every form submission.

Your lead flow lives across a dozen tools: a CRM here, a spreadsheet there, a notification somewhere else. FormWire triggers your Zaps on every submission, so those tools update themselves, while the email and the stored record land as usual. One POST, wherever your workflow reaches.

Get your access key → See how it works

Wherever your workflow reaches

What your Zaps receive on each submission.

A new-submission trigger

Each submission fires FormWire's Zapier trigger with your form's fields mapped and named, so the Zap starts on clean data, not a raw payload.

Reach thousands of apps

From the trigger, a submission can flow to any app Zapier connects (CRMs, task managers, team chat) through the Zaps you already run.

Fan out to many Zaps

Point several Zaps at one form's trigger: copy the lead to a CRM, log a row in a sheet and ping a channel, all from the same submission.

Spam never spends a task

Filtered submissions don't fire the trigger, so your Zapier task quota goes to real leads instead of bot runs.

Set up in under a minute

Connect FormWire to Zapier in 3 steps.

Connect from the form
Open your form's Integrations tab and connect Zapier. The connection is native and configured per form, so each form can drive its own workflow.
Choose the trigger
In your Zap, pick FormWire's new-submission trigger. Each submission that passes spam checks starts the Zap in real time.
Map your fields
Match your form's fields to the apps in your workflow — name to a CRM contact, message to a task, email to a follow-up. Zapier handles the rest.

Zapier integration FAQ

Setup, triggers and the details that matter.

Want a different destination?

All integrations

Route submissions elsewhere too.

All integrations

Slack, Sheets, webhooks and more.

Webhooks

Skip Zapier entirely for custom code.

Google Sheets

Or write rows directly, no Zap needed.

Pricing

See which plan includes Zapier.

Ready in a minute

Wire every submission into your Zaps.

Connect Zapier once, and every submission that clears spam can fan out across the tools your workflow already runs.

Get your access key → Read the docs