Every Zapier limit, by plan
Last verified
Zapier's limits come in three layers. Plan limits set how many tasks you can run per month and how often polling triggers check for new data. As of November 2026, Free includes 100 tasks a month with 15-minute polling and two-step Zaps. Professional checks every 2 minutes, and Team and Enterprise check every minute. Zap limits apply to everyone: 100 steps per Zap, 1,000 fields per action step, and rate limits on how fast triggers can start Zaps. Runtime limits cap individual steps. App actions must finish in 30 seconds, Code by Zapier steps get 1 second on Free, 30 seconds on Professional and Team, and 2 minutes on Enterprise, and webhook payloads are capped at 10 MB for triggers and 5 MB for actions.
A task is counted each time an action step runs successfully. Triggers, filters and some built-in steps don't count. When you run out, Zapier holds Zap runs rather than dropping them. On paid plans, pay-per-task billing can keep Zaps running past the limit at a higher per-task rate.
Values come from zapier.com/pricing, the Zapier Help Center and Zapier's developer platform documentation, verified November 12, 2026. Prices and task tiers change often; check the pricing page before buying.
Official reference: Zapier Help Center - Zap limits
Jump to: Tasks and polling interval by plan (as of November 2026) · Zap structure and trigger rate limits · Timeouts, Code by Zapier and payload sizes · When you hit a limit · Staying under it
Tasks and polling interval by plan (as of November 2026)
Paid plans are sold in task tiers, so the price depends on the monthly task volume you pick. The polling interval is how often Zapier checks a polling trigger (for example "New Row in Google Sheets") for new data. Instant (webhook-based) triggers fire immediately on every plan. Code by Zapier's included runtime also scales with the plan, which matters for scripts that call slow APIs.
| What | Limit | Source |
|---|---|---|
| Free | 100 tasks/month; 15-minute polling; two-step Zaps only | docs ↗ |
| Professional | 750 to 2,000,000 tasks/month; 2-minute polling; multi-step Zaps | docs ↗ |
| Team | 2,000 to 2,000,000 tasks/month; 1-minute polling; multi-step Zaps | docs ↗ |
| Enterprise | Custom annual task limit; 1-minute polling | docs ↗ |
| Pay-per-task overage (paid plans) | 1.25x base rate (annual) or 2.5x (monthly) | docs ↗ |
| Task limit warnings | Emails at 80% and 100% | docs ↗ |
Zap structure and trigger rate limits
These limits are enforced per Zap or per user regardless of plan, except where noted. The trigger rate limits protect Zapier and the connected apps from floods. When a Zap exceeds one, its runs are held, or the request gets a 429 for instant triggers, rather than silently dropped. Flood protection is a separate safeguard: if a polling trigger suddenly returns 100 or more new items at once, Zapier holds them and asks you to confirm before replaying.
| What | Limit | Source |
|---|---|---|
| Steps per Zap | 100 | docs ↗ |
| Fields per action step | 1,000 | docs ↗ |
| Instant (webhook) triggers | 20,000 requests every 5 minutes per user | docs ↗ |
| Polling triggers on Free or trial plans | 200 requests every 10 minutes per Zap | docs ↗ |
| Private apps | 100 requests/60 seconds (Free, Professional); 5,000 requests/60 seconds (Team, Enterprise) | docs ↗ |
| Flood protection | 100+ trigger events at once are held | docs ↗ |
| Polling trigger items per poll (default) | 100 new items | docs ↗ |
| Deduplication table | 105,000 rows per Zap | docs ↗ |
Timeouts, Code by Zapier and payload sizes
Every app action, search and polling trigger has 30 seconds to finish its requests and scripting. That window is fixed, and slow third-party APIs are the most common cause of timeout errors. Code by Zapier steps have plan-based runtimes and 512 MB of memory. On paid plans you can opt individual steps into extended runtime, billed in extra tasks. Webhooks and step inputs have size caps, but files are passed between steps by reference and don't count against input payload limits.
| What | Limit | Source |
|---|---|---|
| App action / search / polling trigger time limit | 30 seconds | docs ↗ |
| Code by Zapier standard runtime | Free 1 second; Professional 30 seconds; Team 30 seconds; Enterprise 2 minutes | docs ↗ |
| Code by Zapier extended runtime | Up to 10 minutes total (paid plans) | docs ↗ |
| Code by Zapier memory | 512 MB (all plans) | docs ↗ |
| Code by Zapier rate limit | Free 10 per 60 seconds; Trial 75 per 10 seconds; Professional, Team, Enterprise 225 per 10 seconds | docs ↗ |
| Webhooks by Zapier payload | 10 MB for triggers; 5 MB for actions | docs ↗ |
| HTTP response payload (developer platform) | 20 MB | docs ↗ |
| Downloaded files (developer platform) | About 120 MB | docs ↗ |
What happens when you hit a limit
Task limit: Zapier holds the actions of all Zaps in the account once the billing cycle's task limit is reached, unless pay-per-task applies. Trigger data keeps being stored, and held runs can be replayed after you upgrade or the cycle resets, so no data is lost. Upgrading resets task usage.
Rate limits: instant triggers over 20,000 requests per 5 minutes get HTTP 429. Polling triggers and Code steps over their limits have their runs held until the limit resets.
Timeouts: a step that runs past 30 seconds fails, typically with The app did not respond in-time. It may or may not have completed successfully. Because the request may have succeeded on the app's side, check before replaying. A Code step past its runtime "fails with a timeout error."
Payload size: oversized webhooks return 413.
Staying under the limits
Cut task usage. Put Filter steps early, since filters don't use tasks and they stop runs before paid actions, and combine several updates into one action where the app supports it.
Pick instant triggers (webhooks) over polling triggers where an app offers both. They fire on every plan without waiting for the polling interval.
Split slow work. If an app call takes longer than 30 seconds, start the job in one Zap and pick up the result in a second Zap triggered when the job finishes, instead of waiting inside a step.
Use extended runtime for heavy Code steps on paid plans, or move heavy processing out of Zapier.
Upgrade or enable pay-per-task when volume is the real constraint. Higher tiers also shorten polling to 2 or 1 minutes.
Zapier errors and guides
Other platforms
Frequently asked questions
How many tasks does the Zapier free plan include?
100 tasks per month as of November 2026, with two-step Zaps only and a 15-minute polling interval. A task is one successful action step; triggers and filters don't count. When the free plan reaches its limit, Zap runs are held until the next cycle, because pay-per-task billing is only available on paid plans.
How often do Zapier triggers check for new data?
Polling triggers check every 15 minutes on Free, every 2 minutes on Professional, and every minute on Team and Enterprise. Instant triggers, which receive webhooks from the app, run as soon as the event arrives on every plan. Whether a trigger is polling or instant is set by the app's integration.
What is the maximum number of steps in a Zap?
100 steps, including every step inside Paths. During a free trial only the first 30 steps of a Zap run. The Free plan is limited to two-step Zaps (one trigger, one action); multi-step Zaps require a paid plan. Each action step can have up to 1,000 fields.
What is the Zapier action timeout?
30 seconds. Zapier's developer documentation sets a 30-second limit for each create or search action, each polling trigger, and the Test step in the Zap editor, covering both requests and scripting. When an app is slower than that, the step fails with a timeout error even if the app later completes the request.
How long can a Code by Zapier step run?
Standard runtime is 1 second on Free, 30 seconds on Professional and Team, and 2 minutes on Enterprise, with 512 MB of memory on every plan. Paid plans can opt individual steps into extended runtime of up to 10 minutes total, billed at one extra task per additional 30 seconds.
What happens when I run out of Zapier tasks?
Zapier holds Zap runs instead of running their actions, and keeps storing trigger data. You can upgrade, which resets task usage, or wait for the billing cycle to reset, then replay the held runs. Paid plans with pay-per-task keep running past the limit at 1.25x (annual) or 2.5x (monthly) the base rate, up to 3x your subscription.
What is the Webhooks by Zapier size limit?
10 MB for webhook triggers and 5 MB for webhook actions. Payloads above that receive a 413 status code. Zapier's developer platform separately lists a 20 MB HTTP response limit and about 120 MB for downloaded files, and passes files between steps by URL rather than inside the payload.
Pace the work instead of tripping the limit
Autonoly workflows run on a schedule or a trigger with per-node retries and timeouts, so a job can be spread out and retried rather than run in one burst. Platform limits still apply in full; no tool can lift them.