Rate Limiting#

Zapier Throttling#

For users on free plans and free trials, 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 minute 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/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 those unintended tasks in the action service.

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

Note: 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 actively - 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 a industry standard exponential backoff interval for retries.

↑ Was this documentation useful? Yes No (Suggest Edits)
Get Help