openwebhook.co
Open inspector →
developer guide

How to Test Webhooks in Make

Inspect the HTTP Make sends with the HTTP module. Custom webhook is Make’s inbox; use an inspector URL when Make is the sender.

By David Lorenzo García··5 min read

Make has two webhook stories. Custom webhook is a trigger: Make gives you a URL and Determine data structure captures what you send in. OpenWebhook is the other direction: Make as the sender, so you can see the exact request an HTTP module fires.

Open the inspector and keep the tab visible. The generic inspector flow is in how to test webhooks online.

HTTP module → inspector

  1. After your trigger, add HTTP → Make a request.
  2. Method POST (or whatever the destination requires).
  3. URL:
https://hooks.openwebhook.co/YOUR_UUID/make
  1. Body type JSON. Map scenario variables into the body. Add headers the real API will need.
  2. Run once (or use Run this module only).

The inspector should show POST /make, Make’s user agent, your headers, and the JSON. If the module reports an error but the inspector is empty, the request never left Make (wrong URL, scenario off, or a filter).

Custom webhook (Make as receiver)

Add Webhooks → Custom webhook, copy Make’s URL, then Determine data structure. Send a sample to Make with cURL or the inspector’s copy-as-cURL against that Make host. That path does not use hooks.openwebhook.co as the destination.

When to use the CLI

Point the HTTP module at a CLI listen URL when the next consumer is a local server. The public status then comes from 127.0.0.1, not from a stored custom response.

Related guides