Prompt
Zapier webhook trigger not firing
Latest observation
Oct 5, 2026
OpenAI APIWeb search: off
If a Zapier webhook trigger isn’t firing, it usually comes down to one of a few things:
Quick checks
-
Make sure the Zap is turned on
- In Zapier, the Zap must be enabled for the trigger to listen.
-
Confirm you’re using the correct webhook URL
- For Catch Hook triggers, verify the exact URL in Zapier.
- Any typo, old URL, or staging/prod mix-up will prevent hits.
-
Check that the request is actually being sent
- Use your app logs, browser dev tools, or Postman/cURL to confirm the webhook call is happening.
- A webhook that never leaves the source system can’t trigger Zapier.
-
Verify the request method and content
- Zapier webhooks generally expect a valid HTTP request.
- Commonly this is a POST request with the right body format.
-
Look at the Zapier task history
- If Zapier received the webhook but the Zap didn’t continue, task history may show the issue.
- If there’s nothing there, Zapier likely never received the request.
-
Check for filters or paths in the Zap
- A filter step may be stopping the Zap after the trigger fires.
- Paths can also route the event away from the expected action.
-
Test with a known-good request
- Send a simple test payload directly to the webhook URL using cURL or Postman.
- Example:
curl -X POST 'YOUR_ZAPIER_WEBHOOK_URL' \ -H 'Content-Type: application/json' \ -d '{"test":"hello"}'
-
Make sure the payload is valid
- Invalid JSON, malformed headers, or empty bodies can cause issues depending on your setup.
-
Check for rate limits or authentication requirements
- If the source app requires auth/signatures, make sure those are correct.
- Some services retry or fail silently if auth is wrong.
-
Wait a minute and refresh
- Sometimes Zapier is a little delayed in test mode or while polling/processing.
If this is a “Catch Hook” trigger
- Go to the trigger step and click Test trigger
- Make sure Zapier is actively waiting for a sample
- Then send the webhook again
If this is a “Retrieve Polling” trigger
- It’s not a real webhook listener
- Polling triggers check on a schedule, so they won’t fire instantly
If you want, I can help you troubleshoot it step by step. Paste:
- the Zapier trigger type
- the webhook source
- a sample payload
- whether this is test or live mode