Website form to Make webhook: run a scenario for each submission
Make (once called Integromat) starts a scenario whenever its custom webhook receives a request. Paste that webhook's address into Anticode's webhook connector and each booking, enquiry, sign-up and invite request from your published sites runs the scenario, with the visitor's fields ready to map into later modules.
What you're building
The chain is short. A visitor sends a form on your Anticode site; Anticode saves it; within about a minute Anticode's server posts it as JSON to your Make webhook; Make queues the request and runs the scenario. Everything after the first module is yours: write to a database, create an invoice draft, post to a team tool, or route bookings and enquiries to different people. A website form to Make webhook setup is the right choice when the logic has several steps or touches apps Anticode has no connector for.
Create the webhook in Make
- In the scenario builder, add the Webhooks › Custom webhook module as the first module.
- Next to the Webhook dropdown choose Add, give it a name such as "Anticode forms", and save. Leave API Key authentication off (see below).
- Make generates the URL and starts listening. Click the address to copy it.
- In Anticode, open Connectors › Webhook, paste the URL and press Save and turn on.
- Back in Make, keep the module listening and press Send a test in Anticode. Make reads the sample request and learns its fields.
These steps follow Make's Webhooks app documentation. The test request from Anticode is a contact form, so the module will know name and message but not the booking fields. Submit your live booking form once, then use Detect new values in the module settings and send another request so Make picks up service, day, time and phone too. For validation, define a data structure under the webhook's advanced settings instead.
Mapping the fields
After detection, Make shows the request as a bundle you can map from:
| Item | Use it for |
|---|---|
| event | Ignore; it is always form.submitted |
| site | A router or filter when several sites share the account |
| form | Filtering: booking, contact, subscribe or signin (fn:<name> for a custom form) |
| data › email | The visitor's address, present on every built-in form |
| data › name, phone | Booking and contact forms only (phone on bookings) |
| data › service, day, time | Bookings only; day is YYYY-MM-DD |
| data › message | Contact forms only |
| submittedAt | An ISO timestamp in UTC; parse it with Make's date functions |
Put a router straight after the webhook with one route per form value. That keeps a newsletter sign-up from ever reaching the module that expects a phone number.
Settings that will block Anticode
- API key authentication. Make can require a key on incoming requests. Anticode's connector sends no custom headers, so with this on every delivery is refused. Rely on the URL's secrecy instead.
- IP restrictions. Make lets you allow-list IP addresses. Anticode doesn't publish a fixed list of sending addresses, so leave the restriction empty.
- An idle webhook. Make deactivates a webhook that hasn't been attached to a scenario for more than five days and then answers
410 Gone. If you made one and left it unused, create a new one.
Delivery behaviour
According to Make’s webhooks help page, without a Webhook response module Make answers an accepted request with HTTP 200 and the body "Accepted", and keeps the data in the webhook's queue even if the scenario can't run straight away. That suits Anticode well, because Anticode only needs a 2xx answer within five seconds and doesn't read the body. Anticode sends each submission once and doesn't retry, so if Make is unreachable at that moment, the submission stays only in your Anticode Submissions. Make's queue covers the other half: once Make has accepted a request, it waits there for the scenario.
Keep the address private
Anyone with the webhook address can start your scenario and spend your operations. Anticode encrypts the URL when you save it, shows only that one is saved, and never puts it in the builder or a published page. If it leaks, delete the webhook in Make, create a new one and paste the replacement.
Compare the same setup in Zapier and n8n, or read the full webhook connector reference for the URL checks.
Questions people ask
Do I need a paid Make plan?
Make's custom webhook is a built-in module; check Make's own pricing for how many operations your plan includes, since every submission runs the scenario.
Can Make return a message to the visitor?
Not through this connector. Anticode ignores the reply. Site functions can show text from your endpoint on the thank-you page.
Is Integromat the same thing?
Yes. Integromat was renamed Make, and its webhooks work the same way for this purpose.
Sources
- Make Apps: Webhooks (custom webhook module), checked
- Make Help Center: Webhooks, checked