Sending WordPress contact form entries to a Zapier webhook
In Zapier, start a Zap with Webhooks by Zapier → Catch Hook, copy the URL it gives you, and paste it into your form plugin's webhook setting. Each entry is then posted to Zapier as JSON, and the Zap can send it anywhere — Google Sheets, Salesforce, Slack, Microsoft 365.
When a webhook is the right route
Use a webhook for services a form plugin doesn't connect to directly, especially those that need an OAuth app: Google Sheets, Salesforce, Microsoft, Constant Contact, AWeber. Zapier holds those logins, and your form only needs one URL.
Setting it up with Mailbag Pro
- In Zapier, create a Zap with the Catch Hook trigger and copy its URL.
- In Mailbag Pro — the paid add-on to Mailbag Contact Form — add a webhook connection with that URL and, if you like, a secret.
- Press Test: Pro posts a small test message so Zapier can learn the shape of the data.
- Choose which forms use the webhook, and which fields it receives.
Each entry is posted as JSON with the fields you chose. With a secret set, each request carries an X-Mailbag-Signature header — an HMAC-SHA256 made with your secret — so a step in your Zap or your own endpoint can check that the request really came from your site.
When the Zap is off
Zapier answers 410 Gone when a Zap is turned off or deleted. Many plugins ignore the answer, and entries vanish. Mailbag Pro treats it as a broken connection: it keeps the entries, emails you — at most once a day — and sends them when the hook works again. Other failures, such as Zapier being unavailable, are retried after 5 minutes, 30 minutes, 2 hours, 12 hours, then daily for up to 7 days.
Only 2xx counts
An entry is marked sent only when Zapier answers with a 2xx status. A timeout, an error page or an empty answer isn't mistaken for success. See Mailbag Pro and pricing.
This is Mailbag Pro, the paid add-on to the free Mailbag Contact Form plugin. See what it costs, and what happens if you ever stop paying.
Mailbag Pro and pricing