Try or ByeTry or Bye

Make Webhook Not Triggering Scenario

Workaround available Web Updated October 21, 2026

Quick answer

A Make webhook that doesn't start the scenario usually means the scenario is off or scheduled rather than instant, the data structure is stale, or the webhook was deactivated. Turn the scenario on with 'Immediately' scheduling, re-determine the data structure and check the webhook's Logs and Queue.

Most likely fix: Turn the scenario on and run it immediately.

Symptoms

The scenario runs when you click 'Run once' but not automatically; the sender says it delivered but no execution appears; a webhook that worked for weeks suddenly stops.

Why it happens

  • Scenario is turned off or set to a schedule instead of running immediately
  • Webhook data structure changed and needs to be re-determined
  • Webhook was deactivated after 5 days without an assigned scenario (returns 410)
  • Requests piling up in the webhook queue from a previously disabled scenario
  • Sender posting to an old or wrong URL, or a Make-side incident

How to fix it

Try these in order — the most common fix is first.

  1. 1. Turn the scenario on and run it immediately

    1. Open the scenario
    2. Switch the scheduling toggle ON
    3. Click the clock on the webhook trigger and choose 'Immediately as data arrives'
    4. Save the scenario

  2. 2. Check the webhook's Logs and Queue

    1. Go to Webhooks in the left menu and open your webhook
    2. Open the Logs tab and look at the status code of recent requests
    3. Open the Queue tab; if items are waiting, process or delete them
    4. Look for 410 (deactivated), 400 'Queue is full' or 429 (rate limit) responses

  3. 3. Re-determine the data structure

    1. Click the webhook module in the scenario
    2. Click 'Redetermine data structure'
    3. Send a fresh request from the source app
    4. Confirm the module shows 'Successfully determined', then save

  4. 4. Test the URL independently

    1. Copy the webhook URL
    2. Send a test POST with Postman or curl
    3. If Make receives it, the problem is in the sending app's configuration

  5. 5. Recreate the webhook

    1. Delete the webhook module from the scenario
    2. Add a new Custom webhook and create a new URL
    3. Update the URL in the sending app
    4. Check status.make.com if it still fails

This guide also covers

  • make webhook not triggering
  • make.com webhook not working
  • make webhook only runs once
  • make webhook stopped working

Still not working?

If Make keeps failing, you're not alone. See every Make problem users report or the alternatives people switch to.

Other Make errors