Connect your forms to Zapier

A catering firm taking event enquiries wants each one in the shared quotes sheet and in the kitchen's Slack channel before anyone has read it. Zapier does that carrying. formformform supplies the starting gun — a submission — and Zapier's own apps take it from there.

The connection has one trigger, New Submission, and it is instant: a Zap subscribes to a specific form, and the submission is pushed out as it lands rather than picked up on a polling schedule. Movement runs one way. A submission sets off an action somewhere else; nothing in Zapier writes back into a form.

Authorisation is per account, not per form. Do it once and every form you own becomes selectable inside Zapier; you choose which one a given Zap watches later.

Create a Zap on Zapier and search for formformform. New Submission is the only trigger, so there is nothing to weigh up. Under it, a form dropdown lists the forms on your account, newest first — pick the one the Zap should watch.

Every submission to that form fires it, no matter how it arrived: the shared link, a QR code, an embed, a popup. Turning the Zap on subscribes it; turning the Zap off unsubscribes it.

Each submission arrives as one flat record. Six keys are always there — id, submitted_at, form_id, form_public_id, form_title and form_slug — followed by one key per answer field, taken from the field's own label in lower case with underscores. "Event date" becomes event_date. Two fields sharing a label get a numbered suffix on the second.

formformform hands Zapier the field list as soon as you pick the form, so the whole record is mappable before you run a test. Headings, paragraphs, dividers, images, page breaks and submit buttons collect no answer and never appear. Hidden fields do collect one, so a hidden field capturing utm_source arrives like any other value.

A File Upload field — the single type in the palette's Upload section — sends the stored file's identifier, not the file itself. A Zap can record that something was attached, but it cannot hand the bytes to Google Drive or Dropbox. Download or preview the file from the Submissions tab of the form instead, where it stays owner-only.

An encrypted form gives Zapier even less, by design. The answers are encrypted in the respondent's browser, so the only output field is Encrypted Payload (PGP): one opaque blob. Zapier has no key and cannot open it. Anything that needs field-by-field automation has to run on an unencrypted form.

Two screens list running subscriptions. Settings → Zapier groups them all by form. Inside a single form, the Settings tab has an Integrations sub-tab — alongside General, After Submission, Notifications and Encryption — with "Active Zaps for this form" and the same connect button.

Each row shows the Zapier address it delivers to and a Revoke button. Revoking confirms first, then stops delivery straight away. It is the blunt end of the same switch as turning the Zap off in Zapier.