Automation Answers

Why Is My Make Webhook Not Receiving Data?

A Make webhook receives no data when the sender uses the wrong URL or method, the scenario is not listening or active, a proxy blocks the request, or the.

By Automation Ace Editorial TeamReviewed for technical accuracy by Troy TessalonePublished Updated

Short answer

Why Is My Make Webhook Not Receiving Data?

A Make webhook receives no data when the sender uses the wrong URL or method, the scenario is not listening or active, a proxy blocks the request, or the sender never dispatched the event. Put the scenario in Run once, send a fresh event, inspect the sender response and Make webhook log, then verify the exact production webhook URL.

Common causes

  • The request targets an old, copied, or development webhook URL.
  • The scenario is inactive and the webhook queue is disabled or full.
  • The sender uses an unsupported method, content type, or malformed body.
  • The source app never emitted the event or rejected the endpoint.

Diagnostic steps

  1. Click Run once so Make actively listens for a fresh sample request.
  2. Send a controlled event and record the sender timestamp, HTTP status, and response body.
  3. Compare the destination URL character for character and inspect any proxy or firewall logs.
  4. Once captured, redetermine the data structure if the payload fields changed, then activate scheduling.

Example

A form still posts to a webhook created in a deleted scenario. The form reports success locally, but Make shows no request. Replacing the endpoint restores delivery.

Caveats

Webhook payloads can contain customer data. Redact secrets before sharing logs and avoid repeatedly submitting real transactions.