Make webhooks
Make webhooks are the HTTP requests a Make scenario sends to your endpoint through the HTTP app's Make a request module, in whatever shape the scenario builds.
These pages cover requests a Make scenario sends to your endpoint. To send data into Make and trigger a scenario, see Make's Webhooks docs and how to solve Make webhook rate limit errors.
How Make webhooks work
A scenario calls your endpoint as soon as it has data, so your app doesn't have to poll for it. The Make a request module runs once for each bundle it processes, so an earlier module that outputs 50 bundles sends 50 requests. The URL must be HTTPS, and Make rejects self-signed certificates.
Make defines no event types, envelope or version for these requests. The scenario's builder chooses the method, headers, query parameters and body, which can be JSON, multipart/form-data, application/x-www-form-urlencoded or a custom content type. To route requests, put an event name and a stable id in the body yourself.
Key facts
SENDER-DEFINED Content type: application/json, multipart/form-data, application/x-www-form-urlencoded.
Setting up Make webhooks
- In a scenario, add HTTP > Make a request, then set the URL, method, body content type and body. Use a Data structure for JSON bodies, because Make then escapes reserved characters in mapped values for you.
- Set Authentication type to API key and create a keychain placed in the header. If the keychain has Restrict requests to service URLs on, add your endpoint's origin to Allowed service origins.
- Make's cloud can't reach localhost, so test through a public HTTPS URL.
hookdeck listen 3000 makegives you one and forwards requests to your machine. - Resend with scenario run replay, which runs the current scenario again using a past run's trigger data.
Delivery behaviour
1 to 300 seconds set on each module; Make doesn't document the default Retries up to 8 reruns at scenario level, after connection, rate limit and timeout errors; the module has no retry setting Scenario disabled after 3 errors in a row by default, or at the first error if the scenario starts with an instant trigger Ordering parallel by default instant scenarios overlap unless Process data in order is on, and reruns arrive later Known failure modes
From Hookdeck's Make guide →-
Your outage disables the scenario
Make disables a scenario with an instant trigger at its first error, and a scheduled one after 3 errors in a row by default. Store incomplete executions so failed runs are kept and retried.
Retries and disabled scenarios → -
A failed request doesn't stop the scenario
The scenario stops on a
Make failures visible →4xxor5xxonly if Return error if HTTP request fails is set to Yes. Set it, so failures show up in the scenario's history. -
The same request arrives twice
Make can rerun the module after a timeout, even if your endpoint finished the work, and a replay sends the request again. Put a stable
Handle duplicates →idin the body and deduplicate on it. -
Requests with nothing to route on
Make adds no event name, so nothing tells your endpoint which scenario sent a request unless the body says so. Add an
Name your events →eventfield to every body.
Make webhook best practices
- Name the event in every body.
Make adds no event field. Send
eventand a stableid, and keep the shape the same across scenarios so one receiver can handle them all. - Return a 2xx quickly. A slow response holds up the scenario until the module's timeout. Store the request, respond, and do the work afterwards.
- Deduplicate on your own id.
A rerun or a replay sends the request again. Take
idfrom the record the scenario is handling, then skip ids you've processed. - Decide how failures should behave.
Turn on Return error if HTTP request fails and Store incomplete executions, or add error handlers, then test what the scenario does when your endpoint returns a
500. - Keep the key in a keychain. Make recommends the Credentials field over Headers or query parameters. Rotating a keychain under Keys updates every module that uses it.
In this hub
| MCP events → | How an agent subscribes to Make events as MCP events. |
| Verify signatures → | Signature facts, verification code and common failures. |
| Production guide → | Production problems, such as timeouts and retries, and how to handle them. |
| Agent skill → | Install the webhook skill in your coding agent. npx skills add hookdeck/webhook-skills --skill make-webhooks |
Keep an outage on your side from disabling a Make scenario.
Event Gateway accepts each request from the module as it arrives, queues it and retries to your service on your schedule, so your downtime doesn't become an error in the scenario.