# 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](https://help.make.com/webhooks) and [how to solve Make webhook rate limit errors](/webhooks/platforms/how-to-solve-make-com-webhook-rate-limit-errors).

Agent skill: `npx skills add hookdeck/webhook-skills --skill make-webhooks` ([details](https://hookdeck.com/webhooks/make/skill))

> Independent reference generated from hookdeck/webhook-registry (commit ff7f882, 20 Nov 2026). [Make's official docs](https://apps.make.com/api-key-authentication-type).

[Overview](https://hookdeck.com/webhooks/make) · [MCP events](https://hookdeck.com/webhooks/make/mcp-events) · [Verify signatures](https://hookdeck.com/webhooks/make/verify) · [Production guide](https://hookdeck.com/webhooks/make/guide-duplicates-ordering-retries-timeouts) · [Agent skill](https://hookdeck.com/webhooks/make/skill)

## Key facts

| Fact | Value | Source |
|---|---|---|
| Signature header | `None (unsigned)` | [Make docs](https://apps.make.com/api-key-authentication-type) |
| How events are identified | `None from Make: the scenario chooses the body` | [Make docs](https://apps.make.com/http) |
| Body format | `SENDER-DEFINED` Content type: application/json, multipart/form-data, application/x-www-form-urlencoded. | [Make docs](https://apps.make.com/http) |
| Agent skill | `npx skills add hookdeck/webhook-skills --skill make-webhooks` | [Agent skill →](https://hookdeck.com/webhooks/make/skill) |

[Verify Make webhooks](https://hookdeck.com/webhooks/make/verify)

## 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.

## 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 make` gives you one and forwards requests to your machine.
- Resend with [scenario run replay](https://help.make.com/scenario-run-replay), which runs the current scenario again using a past run's trigger data.

## Delivery behaviour

- **Timeout:** 1 to 300 seconds. set on each module; Make doesn't document the default. [Guide](https://hookdeck.com/webhooks/make/guide-duplicates-ordering-retries-timeouts#timeouts)
- **Retries:** up to 8 reruns. at scenario level, after connection, rate limit and timeout errors; the module has no retry setting. [Guide](https://hookdeck.com/webhooks/make/guide-duplicates-ordering-retries-timeouts#retries)
- **Scenario disabled:** after 3 errors in a row. by default, or at the first error if the scenario starts with an instant trigger. [Guide](https://hookdeck.com/webhooks/make/guide-duplicates-ordering-retries-timeouts#retries)
- **Ordering:** parallel by default. instant scenarios overlap unless Process data in order is on, and reruns arrive later. [Guide](https://hookdeck.com/webhooks/make/guide-duplicates-ordering-retries-timeouts#ordering)

## Known failure modes

1. **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](https://hookdeck.com/webhooks/make/guide-duplicates-ordering-retries-timeouts#retries)
2. **A failed request doesn't stop the scenario.** The scenario stops on a `4xx` or `5xx` only if Return error if HTTP request fails is set to Yes. Set it, so failures show up in the scenario's history. [Make failures visible](https://hookdeck.com/webhooks/make/guide-duplicates-ordering-retries-timeouts#retries)
3. **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 `id` in the body and deduplicate on it. [Handle duplicates](https://hookdeck.com/webhooks/make/guide-duplicates-ordering-retries-timeouts#duplicates)
4. **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 `event` field to every body. [Name your events](https://hookdeck.com/webhooks/make/guide-duplicates-ordering-retries-timeouts#choosing-events)

From [Hookdeck's Make guide](https://hookdeck.com/webhooks/make/guide-duplicates-ordering-retries-timeouts).

## Make webhook best practices

- **[Name the event in every body](https://hookdeck.com/webhooks/make/guide-duplicates-ordering-retries-timeouts#choosing-events).** Make adds no event field. Send `event` and a stable `id`, and keep the shape the same across scenarios so one receiver can handle them all.
- **[Return a 2xx quickly](https://hookdeck.com/webhooks/make/guide-duplicates-ordering-retries-timeouts#timeouts).** 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](https://hookdeck.com/webhooks/make/guide-duplicates-ordering-retries-timeouts#duplicates).** A rerun or a replay sends the request again. Take `id` from the record the scenario is handling, then skip ids you've processed.
- **[Decide how failures should behave](https://hookdeck.com/webhooks/make/guide-duplicates-ordering-retries-timeouts#retries).** 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](https://hookdeck.com/webhooks/make/guide-duplicates-ordering-retries-timeouts#other-limits).** 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](https://hookdeck.com/webhooks/make/mcp-events): How an agent subscribes to Make events as MCP events.
- [Verify signatures](https://hookdeck.com/webhooks/make/verify): Signature facts, verification code and common failures.
- [Production guide](https://hookdeck.com/webhooks/make/guide-duplicates-ordering-retries-timeouts): Production problems, such as timeouts and retries, and how to handle them.
- [Agent skill](https://hookdeck.com/webhooks/make/skill): Install the webhook skill in your coding agent. `npx skills add hookdeck/webhook-skills --skill make-webhooks`
---

Not affiliated with Make. Facts are compiled from public sources and linked inline. [View as JSON](https://hookdeck.com/webhooks/make.json) · [Report a correction](https://hookdeck.com/contact)
