DEV Community

Stackscale
Stackscale

Posted on

Make Webhook Not Receiving Data? Fix It in 5 Minutes

#automation #nocode #ai #tutorial

If you want to fix a Make webhook not receiving data, a seven-point checklist finds exactly where the data stops — no guessing, no code. Run the checks in order, from the outside in, and the first one that fails is your break.

What you need

  • A Make scenario with a webhook module
  • The sending app (a form, a shop, or any app that posts to the webhook) and its delivery log
  • A dummy test payload you can fire yourself

Disclosure: Some links below are affiliate links, meaning StackScale may earn a commission at no extra cost to you.

Get started with Make here: https://www.make.com/en/register?pc=stackscale&affiliateSource=devto

The problem: silence looks the same from every break

A webhook is a URL waiting for data. When nothing lands, Make cannot tell you why — the break could be in the sending app, the URL, the payload, or the scenario, and each one looks identical: silence. So do not guess. Check, in order, from the outside in.

The seven checks, in order

  1. Is the scenario on? — Open the scenario and look at the scheduling switch. A scenario that is off never listens. Switch it on, save it, and confirm it is active before you test anything else.
  2. Is the URL copied exactly? — Copy the URL from the webhook module and paste it into the sending app again, character by character. One trailing space or a URL from the wrong environment breaks the chain, and it still looks right at a glance.
  3. Does the request actually fire? — Trigger a real event, submit the test form, or send a manual test request with a dummy JSON payload. Then read the sending app's delivery log. No attempt in the log means the app never sent anything.
  4. Does Make's queue show it? — Open Make's queue and history. A received request shows up with a 200 response. If the queue is empty but the sending app shows a 200, the data reached Make and vanished — look for a filter. A failed run names the module that broke — open it.
  5. Is the data shaped right? — Open a received bundle. Is the body valid JSON, is the content type right, is the body empty? A payload that is not JSON, or a field that arrives blank, fails silently downstream while the webhook itself looks fine.
  6. Has the payload changed? — If the sending app added or renamed a field, old mappings break. Re-determine the data structure with a fresh test request — or delete the old webhook, create a new one, and paste the new URL into the sending app.
  7. Is a filter swallowing it? — Open the execution history and look for runs stopped by a filter, or errors caught and hidden by an error handler. A run that stops here never reaches the next module — that is the silence you have been chasing.

A dummy payload to test with

Fire a test request like this one and watch what Make receives:

{
  "email": "test@example.com",
  "amount": 49.00,
  "source": "demo-form"
}
Enter fullscreen mode Exit fullscreen mode

Check three things about the bundle that arrives: it is valid JSON, the content type is right, and no field arrives blank. If any of those fail, the webhook can look fine while the data is broken.

The finished result

Run the checklist and the webhook receives again — 200 OK, data flowing, no guessing. If a silent webhook has bitten you before, run the checks in this order next time and the break will name itself.

Watch the full tutorial on YouTube: https://youtu.be/HPtL9btenVg — and subscribe to StackScale for a new automation tutorial every day.

Top comments (0)