Webhooks by Zapier rate limits

When you use Webhooks by Zapier in Zaps, if a large number of actions occur within a short time span, they will be throttled (rate limited) to reduce their frequency. 

Rate limits exist to ensure Zapier’s and the app’s infrastructure can efficiently serve all customers.

Note

Zap steps that use other apps may have different rate limits. Learn more about throttling and rate limits for Zaps.

Rate limits

You will see a 429 status code if you exceed these limits:

• 10,000 requests every 5 minutes per user.
• 1,000 requests every 5 minutes per Zap in legacy webhook routes (without a Zapier user ID in the URL).
  • This includes subscriptions and REST webhooks.

Delayed processing

During periods of high webhook activity, Zapier may return a 200 status code but delay webhook processing by several minutes.

If you want to ensure delivery of webhooks:

• Retry delivery on any step that does not have a 200 status code from Zapier. 
• Use industry-standard exponential backoff interval for retries.

What happens if I exceed the limit

If a Zap step exceeds rate limits, you can:

• Replay the Zap run. This will retry the steps in your affected Zap runs.
• Add a Delay After Queue step to your Zap, which pauses actions for a specific time before running them. This will spread out the rate at which the Zap runs those actions.
• Adjust the flood protection limit for a Zap. You must have a paid Zapier plan.