Website form to Zapier webhook: start a Zap from every submission
Paste a Zapier Catch Hook URL into Anticode's webhook connector and every form sent on your published sites becomes a Zap trigger. From there Zapier can do what Anticode's own connectors don't: add a row to a CRM it supports, create a task, send a templated reply, or branch by form. Check your Zapier plan first, because webhooks aren't on its Free plan.
Do you need Zapier at all?
Anticode already sends submissions straight to Slack, Discord, Telegram, Google Sheets, Airtable, Notion, HubSpot, Mailchimp and Kit. If one of those is the only destination, use its connector and skip the extra account. Sending a website form to a Zapier webhook earns its place when you want several steps (log the lead, then create a deal, then post to a channel), a destination Anticode doesn't connect to, such as Pipedrive or Trello, or conditions like "only bookings for the Saturday class".
Plan check
The Catch Hook trigger belongs to Zapier's built-in Webhooks by Zapier app. Zapier's help article on webhook triggers lists it as unavailable on the Free plan and available on Professional, Team and Enterprise. If you're on Free, the direct connectors above are the cheaper route.
Set up the trigger
- In Zapier, create a Zap. For the trigger choose Webhooks by Zapier and the event Catch Hook, then continue. Leave Pick Off A Child Key empty so you receive everything.
- On the trigger's Test tab, copy the webhook URL. It begins
https://hooks.zapier.com/hooks/catch/. - In Anticode, open Connectors › Webhook, paste it into Webhook URL and press Save and turn on.
- Press Send a test in Anticode, then Test trigger in Zapier. You should see one request with a sample contact message.
- Add your action steps, test them, and publish the Zap. Until it's on, live submissions reach the hook but run nothing.
For better sample data, submit your real booking or sign-up form once after the Zap is built, then re-test the trigger and pick that request. Zapier then shows the exact fields that form sends.
What the Zap receives
Anticode posts one JSON object per submission. Zapier splits it into fields you can map in later steps:
- event
- Always form.submitted. Useful only if the same hook also receives other things.
- site
- Your project's name, so one Zap can tell several sites apart.
- form
- booking, contact, subscribe or signin, or fn: followed by the name for a custom form.
- data
- The visitor's fields: service, day, time, name, phone and email for a booking; name, email and message for a contact form; email for a sign-up or invite request.
- submittedAt
- The time the form arrived, in UTC. Use Zapier's Formatter if you need it in your own time zone.
Branch by form
One webhook URL serves all forms on all your sites, so most Zaps start with a filter or paths step. Typical choices: continue only when form is subscribe to send sign-ups to an email tool Anticode doesn't connect; continue only when form is booking and site is your studio's name to create a calendar event; split contact and booking into two paths so they land in different boards. Matching on the form value is reliable because it only ever takes those fixed values.
Reliability and security
- Sent once. Anticode posts each submission a single time, within about a minute. If Zapier answers with an error, Anticode doesn't retry. Zapier holds what it accepted; check its Zap history if a run is missing.
- Sealed URL. The hook URL is all anyone needs to start your Zap. Anticode stores it encrypted and never shows it again or puts it in your pages.
- No redirects. Paste the hook URL exactly as Zapier shows it. A shortened or redirecting link fails.
- Five seconds. Catch Hook replies straight away, so the timeout rarely matters, but a custom endpoint in front of Zapier must answer quickly.
Troubleshooting
- Test trigger finds nothing. Press Send a test in Anticode first, then test in Zapier within a few minutes.
- Live forms don't run the Zap. The Zap is probably still off, or a filter is stopping it. Zap history shows filtered runs.
- Fields are missing in a later step. You tested with the sample contact message; resend a real booking and re-test so Zapier learns the booking fields.
- The URL changed. A copied or rebuilt Zap can have a different hook URL. Paste the current one into Anticode.
The payload and URL rules are covered in full on the webhook connector page. If you prefer other automation tools, see Make or n8n. For lead handling ideas, read sending website leads to a CRM.
Questions people ask
Can I use Zapier's Free plan?
Not for this. Zapier lists Webhooks by Zapier as a paid-plan feature. Anticode's direct connectors don't need Zapier at all.
Can Zapier send a reply back to the visitor's thank-you page?
No. Anticode ignores the webhook's reply. A site function is the way to show computed text on the thank-you page.
Can I have two Zaps for two sites?
There's one webhook URL per Anticode account. Use one Zap with paths that branch on the site field.