Rate limits and throttling in Zapier

Last updated:
Limits: Tasks, Zaps, Third-Party APIs

Limits: Tasks, Zaps, Third-Party APIs

When a large number of triggers or actions occur within a short time span, they are throttled (limited) to reduce their frequency. This is known as rate limiting and may be applied by Zapier or by your connected third-party app.

Zapier throttling

If you’re on the Free plan or a trial, you'll receive an error that your Zap has been throttled if it attempts to perform too many tasks in a short time span. The limit is approximately 200 attempts every 10 minutes per Zap.

Throttling from third-party services

Many third-party apps and services have their own API limits and throttling mechanisms. To distinguish between third-party errors and Zapier throttling errors, look for "Zapier" in the error message.

Flood protection and held items

If you have a large number of items (100+) that trigger a Zap at once, Zapier holds them for you and sends you an email requesting your confirmation. This helps to prevent a significant number of actions being performed by mistake, which keeps your task usage down and prevents the need to correct any unintended results in the action app.

When these Zap runs are replayed, they are processed at a rate of 1 per second. For example, 1,000 Zap runs will take a little over 15 minutes to complete.


Instant triggers are not subject to flood protection, as each item is sent to the trigger individually. Some exceptions inculde Google Sheets and Google Calendar "New Event" and "Updated Event" instant triggers, which use both webhook and polling techniques.

Webhook throttling

  • Each user’s webhooks are subject to a 429 status code rate limit after 10,000 requests in a 5 minute window. This includes subscription webhooks and REST Hooks.
  • Each individual webhook (both legacy and current) route will return a 429 status code after 30 requests per second to encourage a smooth delivery of hooks instead of massive bursts. This includes subscription webhooks and REST Hooks.
  • Legacy webhook routes without the user ID in the URL will return a 429 status code after 1,000 requests received in a 5 minute window (per webhook route). This includes subscription webhooks and REST Hooks.
  • During heavy periods of sustained webhook activity, Zapier may return a 200 status but still delay the processing of your webhooks by several minutes.
  • If you want to enforce proper delivery of webhooks, retry delivery on anything besides a 200 status code from Zapier and use an industry standard exponential backoff interval for retries.

Invite-only app throttling

When using an invite-only app, you may encounter an error like Dev app App12345API (AppNameHere) throttled (100 script executions per 30 seconds), contact support. This is due to a built-in limit for preventing spam for private apps. Once the app has gone public, this limit on script executions for the app will be lifted.

Need More Help?

Contact Support

Tell us about your problem, and we’ll find you a solution or you can email support.
Get Help

Hire an Expert

We have a directory of professionals across the globe who are ready to help.
Find a Zapier Expert

Zapier Community

Connect with other Zapier users and industry professionals to get help crafting the perfect workflow.
Check out the community