Zapier · HTTP status errors
429 - Too Many Requests
Short answer
A 429 in a Zap means too many requests were sent in a short period and exceeded the rate limit of Zapier or the app. Review the rate limits, then replay the run or add a delay.
VerifiedLast verified
01Error text
429 - Too Many Requests02Likely causes
- You exceed Zapier's rate limit or an app's rate limit.
03How to fix it
- Review Zapier's rate limits to see whether the limit is Zapier's or the app's.
- Replay the Zap run.
- Add a Delay After Queue step to the Zap.
iNotes
Instant triggers return 429 errors above 20,000 requests every 5 minutes per user.
04Official documentation
→Related errors
- 400 - Bad RequestA 400 in a Zap means the server could not understand the request due to invalid syntax. Check for missing values in required fields, invalid characters and incorrectly formatted input.
- 401 - UnauthorizedA 401 in a Zap means the request lacks valid authentication credentials. Reconnect your app account by disconnecting and then reconnecting it.
- 403 - ForbiddenA 403 in a Zap means the server understood the request but refused to fulfill it. Confirm the app account is connected properly and has the required permissions.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Zapier work:Open Zapier jobsZapier rates and salaries