Make.com webhook not receiving data
Updated 2026-08-01
The scenario waits on a webhook and nothing arrives — or items sit in a queue. This is one of the most searched Make.com problems. Start with the URL and the trigger configuration before rewriting the whole flow.
What to verify
Confirm the public webhook URL in Make matches what the sender calls (no old scenario copy, no typo, correct HTTPS URL).
Check whether the scenario is on and whether the webhook module is the trigger. A scheduled scenario will not behave like an instant webhook.
If Make shows items in the webhook queue but the scenario does not process them, look at filters, sleep modules, and incomplete executions on later steps — the receive side may be fine.
When you have an error string
Timeouts, 401 from a verified webhook, or errors on the next module are different problems. Paste the exact message into the free diagnosis rather than mixing "webhook dead" with "mapping failed after receive".
Paste the error for a sourced diagnosis
If you still have the execution log, use the free tool — Make's docs only, every claim linked, or an honest refusal when coverage is missing.
Example you can try: My Make webhook is not receiving data. The scenario uses a custom webhook trigger and stayed empty since yesterday.
Official Make documentation
FAQ
Does Eviverse call my webhook?
No. The free tool only reads text you paste. It does not connect to your Make account yet; monitoring is on a waitlist.
Related guides
- Incomplete executions in Make.com
- Why your Make.com scenario suddenly stopped working
- BundleValidationError on Google Sheets in Make.com
Eviverse is independent and not affiliated with Make. These guides are original explanations with links to Make's public Help Center — not republished documentation.