Sending a Website Form to Make With a Webhook: Map Fields and Test Safely
Short answer: Add a Webhooks > Custom webhook module as the first step of a new Make scenario, copy the URL it generates, and paste that URL into your form tool's webhook setting (Elementor's "Webhook" action, the Gravity Forms or WPForms webhooks add-on, Webflow's form webhooks, and so on). Click Redetermine data structure in Make, submit one realistic test entry, and Make learns the field names. Then add a filter that rejects submissions missing required fields, route anything marked as a test to a sandbox sheet instead of your CRM, optionally reply to the form with a Webhook response module, and protect the URL with a secret value checked inside the scenario.
Create the custom webhook in Make
- In Make, create a new scenario and add the Webhooks app, choosing Custom webhook as the trigger.
- Click Add, give the webhook a clear name such as "Website enquiry form, live", and save.
- Make shows a unique URL. Copy it; this is where the form will send its data.
- Leave the module in "listening" mode for the next step.
Make's webhooks documentation covers the options inside the module, including IP restrictions and whether to pass request headers into the scenario. Turn on header passing if you plan to check a secret header later.
Point the form plugin at the URL
The setting lives in a different place in each tool. Common examples:
- Elementor Pro forms: in the form widget, add Webhook under "Actions After Submit", then paste the URL in the Webhook section. Tick the advanced data option if you want field IDs and metadata.
- Gravity Forms: with the Webhooks add-on, create a feed for the form, set the request method to POST, the format to JSON, and choose "All fields" or select specific ones.
- WPForms: the Webhooks addon adds a webhook section in the form's marketing settings, where you map each field to a key name.
- Contact Form 7: has no built-in webhook; a separate plugin adds one.
- Webflow, Framer and similar builders: look for form webhook settings in site or form settings.
Prefer JSON format where you have a choice. Use simple, lowercase keys such as name, email, phone, service, message, consent. Clear keys make mapping in Make far easier than labels like "Field 7".
Teach Make the data structure
Make needs one real sample to know which fields exist.
- In the Custom webhook module, click Redetermine data structure so it waits for data.
- Submit the form once with realistic test values in every field, including optional ones. Empty optional fields are sometimes left out of the payload, so Make would not learn them.
- Make shows "Successfully determined". Click the module to see the fields.
Repeat this whenever you add or rename form fields. If a new field never appears in later modules, the structure is out of date.
Map fields and check required values
Add the modules that do the real work, for example Google Sheets > Add a row, then a CRM "create contact" module, then a Slack or email notification. When mapping, drag fields from the webhook output into each target field.
Before those modules, put a filter on the connection from the webhook:
emailexists and contains "@"nameexistsconsentequals "yes" if your process depends on it
Submissions that fail the filter simply stop. If you want to know about them, add a second route through a Router that sends rejected entries to a review sheet.
Tidy data on the way through with functions: trim() for stray spaces, lower() for email addresses, and formatting functions for phone numbers. Clean data now saves duplicate contacts later.
Route test data away from live systems
Testing against your real CRM fills it with "Test Test" contacts and may trigger welcome emails to fake addresses. Set up a Router directly after the webhook:
| Route | Filter | Destination |
|---|---|---|
| Test | Email contains "+test" or name equals "TEST" | A sandbox Google Sheet only |
| Live | Everything else (set as the fallback route) | CRM, notifications, auto-reply |
Agree the test convention with your team, for example always using an address like office+test@yourcompany.co.uk. You can keep the test route permanently, which makes future changes safe to try.
Send a response back to the form
By default, Make answers the form's request with a plain "Accepted". If the form needs something specific, add Webhooks > Webhook response at the end of the scenario:
- Status
200and a short JSON body such as{"status":"ok"}for tools that check the response. - A different status, such as
400, on the rejected route, so the form plugin logs the failure.
Most form plugins show their own thank-you message regardless, so you only need this when the form or a developer's script reads the reply. Keep scenarios that respond fast: the form waits for Make, and long chains of modules before the response can slow the submission or time out.
Securing the webhook URL
Anyone who learns the URL can post data to it. Reduce the risk:
- Secret value. Add a hidden field or custom header to the form with a long random value, then filter in Make so only requests carrying that exact value continue.
- Do not expose it in the page. Server-side webhooks from form plugins keep the URL off the visitor's browser; avoid client-side JavaScript that posts directly to Make.
- Spam protection on the form. Keep CAPTCHA or honeypot fields switched on, because the webhook passes on whatever the form accepts.
- IP restrictions. If your web server has a fixed outgoing IP, restrict the webhook to it in the webhook settings.
- Regenerate if leaked. If the URL ends up somewhere public, create a new webhook and update the form.
FAQ
Why does Make show "Accepted" but no scenario run?
The scenario is probably switched off or scheduled rather than set to run immediately. Turn it on and check the scheduling setting so webhook data is processed as it arrives.
Do webhook calls queue if the scenario fails?
Webhook data waits in a queue while the scenario is off or busy, within limits set by Make. Check the webhook's queue in Make if runs seem to be missing.
Can one webhook serve several forms?
Yes. Add a hidden form_name field to each form and use a router to send each one down its own route.
If you would like your enquiry form wired into Make with clean data and safe testing from the start, describe your form and tools to us and we will set it up with you.