Rate limits and throttling in Zapier

Last updated:

Limits: Tasks, Zaps, Third-Party APIs

Your Zaps can run into a number of rate limits—meaning, cases where a trigger or action occurs too rapidly and either Zapier or a connected service will have to limit (i.e. “throttle”) it.

Zapier throttling

For users on the Free plans or a trial period, if your Zaps attempt to perform too many tasks in a short span, you'll receive an error that the Zap has been throttled. That limit is approximately 200 attempts every 10 minutes window per Zap.

Throttling from other services

Some other services have API limits and throttling mechanisms of their own. To distinguish between these errors and Zapier throttling errors, look for "Zapier" in the error message. We do not throttle users without using our name in the error.

Flood protection and held items

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

When released, these tasks will be processed the rate of 1 per second. So 1,000 tasks would take a little over 15 minutes to clear out after releasing.


Instant triggers are not subject to flood protection, as each item is sent to the trigger individually.

Webhook throttling

  • Each users' webhooks are subject to a collective 429 status code rate limit after 10,000 requests in a 5 minute window. This includes subscription webhooks or REST Hooks.
  • Each individual webhook (both legacy and current) route will return a 429 status code after around 30 requests per second to encourage a smooth delivery of hooks vs. massive bursts. This includes subscription webhooks or 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 (this is per webhook route). This includes subscription webhooks or REST Hooks.
  • During heavy periods of sustained webhook activity, we may return 200 status but still delay the processing of your webhooks by several minutes.
  • If you wish to enforce proper delivery of webhooks, please 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 non-public 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