Route your leads through a Make scenario
A webhook is just an address that receives
Nothing here is exotic. A webhook is a web address that can receive a message.
When your form captures a lead, the platform posts that lead's details to the address you gave it, within seconds, with nobody checking anywhere.
Make is interesting because of what happens next. Instead of one hard-wired destination, you get a scenario.
Filter by which site or which service the enquiry mentioned. Split it, add to it, send branches to different places — all without changing a thing on this side.
Building the scenario
The whole setup lives in Make, and it takes about five minutes end to end.
- In Make, click Create a new scenario.
- Add a Webhooks module, choose Custom webhook, then click Add, name it and save.
- Copy the address Make shows you, paste it into the webhook field here, and add the webhook.
- Click Send test lead. Make replies that it has worked out the data structure.
- Add your next module, whether that is a CRM, a spreadsheet or an email, and switch the scenario on.
The signature, and what to do with it
Every payload we send carries a signature header. It is computed from a secret shown to you once, when the webhook is created.
Building a no-code scenario? You can ignore it. If a developer is involved, it is a hex HMAC of the raw request body, and checking it proves the message came from us untouched.
The secret is displayed a single time and never again. If it goes missing, remove the webhook and add it back for a fresh one.
Why routing beats a fixed list
Direct connections exist for the common destinations, and they are the right answer when your needs are simple.
Make earns its place when they are not. Several brands, conditional owners, a warehouse table nobody else supports, a finance system older than all of it.
The trade is plain. A direct connection is a few values pasted once and no upkeep. A scenario is more setup and far more control. Most operators run both.
You can switch between the two whenever you like, because the webhook and the direct connections work independently.
Whatever you build downstream, the source stays tight. Each page with a form is individually built and capped in number by your plan. Each is checked against Google Search Essentials and modern web standards at the compliance gate, before anything publishes.
Updated October 2026
Frequently asked questions
Do I need a paid Make plan?
You need a Make account with a scenario that has a custom webhook module. What that costs is between you and Make.
How do I know Make received the test?
Click Send test lead. Make confirms that it has worked out the incoming data structure for the module.
Can one webhook feed several places?
Yes. That is the point of a scenario. Make can branch a single lead to as many modules as you build.
What if I lose the signing secret?
Remove the webhook and add it again. A fresh secret is issued and shown once.
See it built for your business
Every plan starts with a 15-day free trial — build a site in conversation and watch it pass the compliance gate before you decide.
See plans — from $99/moBuild it compliant from day one
Every page is checked before it goes live, by checks that draw on Google Search Essentials and on our own quality rules.
Start your 15-day free trial →Check a site you already have
Free: is your site safe with Google? Get an SEO + compliance score.
Try the Microsite Compliance Grader →