Feature

Zapier Integration

July 17, 2026

Forms can now trigger a Zapier workflow on every submission, no code required. Set it up with a "Webhooks by Zapier" Catch Hook, the same trigger type Zapier recommends for custom apps like Formtorch.

Setting up a Zap

  1. In Zapier, create a Zap with the trigger Webhooks by Zapier → Catch Hook and copy the hook URL.
  2. In Formtorch, open the form's Integrations page and click Add Destination on the Zapier card.
  3. Paste the hook URL, optionally label it, and save.
  4. Submit a real (non-test) entry to the form, then use Zapier's "Test trigger" to pull in the sample and map fields.

Add Destination dialog for the Zapier card on a form's Integrations page

Each submission is delivered as a signed JSON payload through the same async engine that powers webhooks and Google Sheets: retried automatically on transient failures, with delivery status visible per submission.

Zap limits are workspace-wide

Unlike webhooks and Google Sheets destinations, which are capped per form, Zap slots are shared across your whole workspace:

PlanActive Zaps
FreeNot available
Starter1 across all forms
Pro5 across all forms

Pausing a Zap frees its slot immediately; reactivating re-checks the cap.


For setup details and troubleshooting, see the Zapier integration docs.

We’d love to hear from you

Have feedback on this update, or an idea for a feature you’d like to see? We read every message and genuinely take them into account as we build.

hello@formtorch.com