Zapier

Start a Zap with each new response, then send it to thousands of other apps. Formerie sends a webhook, and Zapier’s Webhooks by Zapier catches it.

We wrote this guide from Zapier’s documentation, and haven’t run it on a real Zapier account yet. Tell us if a step differs. Webhooks by Zapier needs a paid Zapier plan: it isn’t on Free.

Connect your form

1. In Zapier, create a Zap. For the trigger, choose Webhooks by Zapier, and for the event, Catch Hook.
2. Choose Continue, and copy the webhook URL from the Test tab.
3. In Formerie, open your form, then Delivery, and add a webhook with that address.
4. In Formerie, choose Send test. It sends one response with made-up answers, one for each field on your published form.
5. In Zapier, choose Test trigger, and pick the request that arrived.
6. Add your action, and map the fields you want. Answers are under data, then fields.
7. Publish the Zap.

The test has test set to true, and real responses have it false. To keep test sends out of your other apps, add a Filter by Zapier step that continues only when test is false.

About the signature

Catch Hook has no way to check a signature. So the Zapier address is what protects you: keep it private. Anyone who has it could send your Zap fake responses. Formerie shows only the start of it after saving, and keeps it encrypted.

If you need the check, Zapier’s Catch Raw Hook gives the raw body and headers to a Code by Zapier step, where you can use the Node or Python sample. Catch Raw Hook takes up to 2 MB, against 10 MB for Catch Hook. That’s plenty for a form.

If it doesn’t work

• Formerie shows a failed try with status 404: Zapier answers this when a Zap is off or deleted, which can take a few hours to change. Turn the Zap on, and use Resend.
• The webhook pauses: Formerie pauses it after 3 failed deliveries in a row. Fix the Zap, choose Resume, and what waited is sent.

Next: send responses to Google Sheets or HubSpot.