This error means the connected app's API rejected Zapier's request because too many requests were sent in a short period. The fix is to add Delay steps between actions, reduce polling frequency, or batch your operations. Zapier's built-in 30-requests-per-second webhook limit and the connected app's own rate limits both apply.
What does "Rate limit exceeded by app" mean in Zapier?
When Zapier shows "Rate limit exceeded by app," it means the destination app returned an HTTP 429 (Too Many Requests) response. Every API has limits on how many requests you can send per minute, hour, or day. When your Zaps send more requests than the app allows, the app blocks further requests until the rate limit window resets.
This error is especially common with AI APIs (OpenAI, Claude) and CRM platforms (HubSpot, Salesforce) that have strict per-minute rate limits. A single Zap processing a batch of records can easily exceed these limits if it fires multiple actions in rapid succession. Zapier processes triggered records sequentially but does not automatically throttle requests to stay within an app's rate limits.
Zapier also imposes its own rate limits: 30 requests per second per individual webhook and 20,000 requests every 5 minutes across all Zaps. If you hit Zapier's internal limits, the webhook returns a 429 to the sender. If you hit the connected app's limits, the Zap action fails with this error.
Common causes
Multiple Zaps or Zap runs are
hitting the same app's API simultaneously, exceeding its per-minute request limit
A batch of records triggered the Zap, causing
many sequential API calls faster than the app allows
Zapier's 30-request-per-second webhook limit was exceeded by
the trigger source
The connected app reduced its rate limits or
your API plan tier has lower limits than expected
A looping Zap is rapidly
sending redundant requests to the same API endpoint
The app counts Zapier requests
alongside your other API usage (direct calls, other integrations), pushing the combined total over the limit
How to fix rate limit errors in Zapier
Add a Delay by Zapier step before the action that hits the rate limit. Set the delay to spread requests out over a longer time window. For example, if the app allows 60 requests per minute, add a 2-second delay between each action to stay under the limit. For batch processing, use Zapier's Looping by Zapier with a built-in delay to process items one at a time with pauses between them.
Also check if the connected app supports batch operations — sending 10 records in one API call instead of 10 separate calls uses only one request against the rate limit. If you have multiple Zaps hitting the same app, consolidate them into fewer Zaps with Paths to reduce total API calls. For high-volume automations that consistently hit rate limits, RapidDev can help design a queue-based architecture that respects API limits while processing all records.
Prevention tips
- Add a Delay by Zapier step before rate-limited actions to spread requests over a longer time window
- Consolidate multiple Zaps that hit the same app into a single Zap with Paths to reduce total API calls
- Check the connected app's API documentation for its exact rate limits and design your Zap's timing around them
- Use the Zap History to see how many runs occurred in the last hour and compare that to the app's rate limit
Still stuck?
Copy one of these prompts to get a personalized, step-by-step explanation.
My Zapier Zap shows 'Rate limit exceeded by app' when sending data to an API that allows 60 requests per minute. How do I add delays and batching to stay under the limit?
Add a Delay step to my Zap before the API action to limit requests to under 60 per minute, and set up retry logic for any rate-limited requests.
Frequently asked questions
What does "Rate limit exceeded by app" mean in Zapier?
It means the connected app returned an HTTP 429 error because too many API requests were sent in a short period. The app temporarily blocks further requests until the rate limit window resets, typically after one minute.
Does Zapier automatically retry rate-limited requests?
Zapier has built-in retry logic for some HTTP errors, but it does not always retry 429 errors automatically. The Zap run is marked as errored in Zap History, and you can replay it manually or set up auto-replay.
How do I add a delay between Zapier actions?
Add a 'Delay by Zapier' step between your trigger and the rate-limited action. You can set a fixed delay (e.g., 2 seconds) or delay until a specific time. This is a built-in Zapier app available on all plans.
Can Zapier's own rate limits cause this error?
Yes. Zapier limits webhooks to 30 requests per second per endpoint and 20,000 requests per 5 minutes across all your Zaps. If these limits are exceeded, the webhook returns a 429 to the sender.
How do I check the rate limits of my connected app?
Check the app's API documentation for its rate limit specifications. Most APIs state limits in terms of requests per minute or per hour. Some apps also return rate limit headers (X-RateLimit-Remaining) in their responses.
Talk to an Expert
Our team has built 600+ apps. Get personalized help with your issue.
Book a free consultation