Zapier
ProStart a Zap the moment a form is submitted, and hand it every answer.
One licence covers every Pro plugin
Form entry
Zapier
Your Zap
- Version
- 1.0.0
- WordPress
- 6.5+
- PHP
- 7.4+
- Tested up to
- 7.1
- Licence
- GPLv3
What it does
Six thousand apps, no new plugin
Anything Zapier can reach becomes a destination for your forms, without another integration to install and keep updated.
Fields arrive already named
Answers reach the Zap under your own field labels, so building the next step does not mean guessing what field_3 was.
One catch hook per form
Paste the Zapier catch hook URL onto the delivery. Different forms can drive completely different Zaps.
Getting it working
-
01
Create a catch hook Zap
In Zapier, start a Zap with the Webhooks trigger and copy the catch hook URL it gives you.
-
02
Paste it on the form
Add the Zapier delivery to your form and paste the URL in.
-
03
Submit once to teach Zapier the shape
Send a real submission so Zapier can read the fields, then build the rest of the Zap against them.
Every setting
What you can configure, and where it lives. Site settings apply everywhere; the rest are set on the form itself.
| Setting | Scope | Notes |
|---|---|---|
| Catch hook URL | Per delivery | From your Zap’s Webhooks trigger. |
| Included fields | Per delivery | All answers, or a chosen subset. |
Questions
Why use this instead of the Webhooks plugin?
Zapier expects a particular payload shape and this sends it. Webhooks is the general tool for endpoints you control yourself.
Does a failing Zap lose the entry?
No. The entry is stored before deliveries run, and a failed call is recorded against it.
Can I only send some of the answers?
Yes. Choose which fields travel, which is worth doing when a form collects more than the Zap needs.
Is the catch hook URL a secret?
Treat it as one. Anyone holding it can post into your Zap, so it is stored as a delivery setting rather than rendered on the page.
Elsewhere in the pack
Start using Zapier
One licence covers every Pro plugin