Webhooks Make integrationAutomate Webhooks with Make.
Need any tool, form or inbox to start a Make scenario the moment it sends something? The Webhooks Make integration gives you 2 instant triggers and 4 actions for that. This page explains each one in plain words and walks you through a first working scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Webhooks Make integration do for you?
The Webhooks Make integration is a built-in Make app that lets outside tools start your scenarios. A scenario is the automation you build in Make, a chain of modules. With Webhooks, another tool sends data to a unique address, or you forward an email, and the scenario runs as soon as it arrives.
Catch form submissions as they land. Point a website form or any tool that can call a URL at a Custom webhook. Each submission becomes a bundle, one item passed to the next module, ready to be sent wherever you need it.
Turn emails into data. A Custom mailhook receives the emails you send to it. Make splits the sender and the To, CC and BCC addresses into separate values, so a support request or a supplier order can feed the rest of the scenario without copy and paste.
Answer the tool that called you. Webhook response sends a reply back to whoever triggered the Custom webhook, which matters when that tool waits for a confirmation before moving on.
A few limits come from the Make documentation: one webhook belongs to one scenario only, an email sent to a mailhook cannot exceed 25 MB with its attachments, and the header name x-make-apikey is reserved, so its value never reaches you. When something breaks, the Make troubleshooting guide is a good first stop. To learn the editor properly, see our Make training, and if you are also looking at n8n, the n8n vs Make comparison lays out both tools.
How do you set up Webhooks in Make?
- 01
Add the module and click Add
Open your scenario, click the + and search for Webhooks. Pick Custom webhook or Custom mailhook, then click Add (Make may show it as Create a connection). The doc lists no prerequisite: no outside account is needed.
- 02
Name it clearly
Give the webhook a name that says where the data comes from, such as the name of the form or the inbox. That name is optional, but it saves time later when several scenarios sit side by side in your Make account.
- 03
Save and keep the address
Click Save. Make then shows the address to call or to send emails to. Paste it into the tool that will send the data and send one test delivery so you can see what arrives.
Your first scenario with Webhooks
GoalWhen a tool calls your Custom webhook, Make receives the data and sends a Webhook response back to that tool.
- 01
Create the scenario
From the Scenarios page, create a new scenario and click the + in the middle of the editor. This first module decides what starts the whole automation.
- 02
Add Custom webhook
Search for Webhooks, choose Custom webhook, click Add, name it and click Save. Copy the address Make gives you into the form or tool that will send data.
- 03
Add Webhook response
Click the + on the right of the first module and pick Webhook response. Map values from the incoming bundle into the reply so the calling tool gets something useful back.
- 04
Test with Run once
Click Run once, then send one test submission from your tool. Open each module to read the bundles it received and check that the reply carries the values you mapped.
- 05
Switch the scenario on
Turn the scenario on. Custom webhook is an instant trigger, so Make runs the scenario as soon as data reaches the address instead of waiting for the clock on the first module.
What starts a Webhooks scenario
2 modules start a scenario when something happens in Webhooks. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Webhooks as soon as it happens.
Custom mailhook
Instant triggerIn Make“Triggers when mailhook receives data.”
Custom mailhook turns incoming emails into scenario data: forward a message to it and Make starts your scenario with the sender and the recipients ready to map. Handy for inboxes that nobody wants to sort by hand.
Custom webhook
Instant triggerIn Make“Triggers when webhook receives data.”
Custom webhook gives you an address that any tool able to call a URL can use to start your scenario and hand it data. It is the usual way to connect a service that has no Make app of its own.
x-make-apikey is sanitized, so you never receive its value.The other Webhooks modules
Webhooks gives you 4 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.
Make supports the following incoming data formats:
3 modulesQuery string
ActionIn the docs onlyQuery string is one of the incoming data formats the Make documentation lists for Webhooks, next to form data and JSON. The doc names it without describing fields, so treat it as a sign that values passed in a URL are understood by Make.
Form data
ActionIn the docs onlyForm data sits in the same documented list of incoming formats that Make accepts on a webhook. There is no official description beyond its name, which tells you that data posted the way a web form posts it is supported.
JSON
ActionIn the docs onlyJSON completes the trio of incoming formats listed in the Webhooks documentation. The doc gives it no description, only its place in the list, which suggests that structured data sent by apps and scripts can reach your scenario.
Other modules
1 moduleWebhook response
ActionIn Make“Creates a response to the webhook.”
Webhook response lets your scenario answer the tool that called it, instead of leaving that tool with no reply. You place it after Custom webhook and fill the answer with values from earlier modules.
Need help automating Webhooks with Make?
A person reads every message.
