Zapier: 429 from Webhooks by Zapier and instant triggers
Last verified
429 Too Many RequestsWhat it means
When something sends webhooks into Zapier too fast, Zapier answers with HTTP 429. The Zap limits article states that instant triggers return 429 errors once you exceed 20,000 requests every 5 minutes per user, and Zapier's webhook documentation adds a limit of 1,000 requests every 5 minutes per Zap for legacy webhook URLs that do not include a user ID.
The 429 goes back to the sender (your app, form tool or script), not into Zap history, so from inside Zapier the symptom is simply missing runs. The sender must retry, or those events are lost.
Separately, polling triggers on Free and trial plans are held after 200 requests in 10 minutes, and private apps have per-minute limits by plan (100 per 60 seconds on Free and Professional, 5,000 on Team and Enterprise).
What is not wrong: the Zap configuration. Volume is.
What it looks like
POST https://hooks.zapier.com/hooks/catch/123456/abcdef/
HTTP/1.1 429 Too Many RequestsWhy it happens
- A backfill or bulk export posts thousands of events at once.
- A misconfigured sender retries in a tight loop.
- Many Zaps on one account share the per-user limit.
- A legacy webhook URL is subject to the lower per-Zap limit.
How to fix it
- Check the sender's logs for 429 responses from hooks.zapier.com.
- Make the sender retry with exponential backoff instead of dropping events.
- Throttle bulk sends so they stay well under the documented limits.
- Use the current webhook URL format that includes your user ID.
- For large backfills, import data directly into the destination app instead of through Zaps.
How to stop it recurring
Put a queue between high-volume sources and Zapier, batch events where the source supports it, and monitor the sender for 429 responses. Generic retry rules are in HTTP 429.
Official documentation: help.zapier.com/hc/en-us/articles/8496181445261. See all Zapier error messages or the Zapier limits and quotas.
Related errors
Definitions
Quick answers
What does "429 from Webhooks by Zapier and instant triggers" mean in Zapier?
When something sends webhooks into Zapier too fast, Zapier answers with HTTP 429. The Zap limits article states that instant triggers return 429 errors once you exceed 20,000 requests every 5 minutes per user, and Zapier's webhook documentation adds a limit of 1,000 requests every 5 minutes per Zap for legacy webhook URLs that do not include a user ID.
How do I fix "429 from Webhooks by Zapier and instant triggers"?
1. Check the sender's logs for 429 responses from hooks.zapier.com. 2. Make the sender retry with exponential backoff instead of dropping events. 3. Throttle bulk sends so they stay well under the documented limits. 4. Use the current webhook URL format that includes your user ID. 5. For large backfills, import data directly into the destination app instead of through Zaps.
Error handling you can see in the workflow
Autonoly workflows have per-node retries, timeouts, continue-on-fail and error-handler branches, so a failing step can be retried or routed instead of stopping the whole run. Saved workflows have no loop node; lists are worked through by the AI agent or one run per trigger item.
Also see Visual workflow builder.