Blog · Automation · Updated · By the FitMySaaS team
Zapier task limits explained: what counts and what it costs
Short answer: A Zapier task is one action step that runs successfully. Triggers, filters, paths and failed steps do not count. Plans range from 100 tasks a month on Free to 750 on Professional ($19.99/mo) and 2,000 on Team ($69/mo), list price, billed yearly, October 2026. Go over and paid plans bill extra tasks, then pause your Zaps at 3x the limit.
What counts as a task in Zapier?
Zapier defines a task as an action step that runs successfully in another app. Creating a row in Google Sheets or posting to Slack is one task each. Here is what does and does not count, from Zapier's guide to tasks:
| Step type | Counts as a task? |
|---|---|
| Trigger (including polling checks) | No |
| Filter and Paths | No |
| A step that fails | No |
| Built-in tools: Tables, Forms, Delay, Looping, Digest, Manager | No |
| Each successful action step in another app | Yes, 1 task |
| Standard AI by Zapier step | 1 task |
| Advanced AI by Zapier step | 3 tasks |
| Premium AI by Zapier step | 5 tasks |
| Zapier MCP tool call | 2 tasks |
So a Zap with one trigger and four actions uses four tasks every time it runs all the way through.
How many tasks does each Zapier plan include?
Each plan starts at a set number of tasks, and you can pick a higher task tier for more money. Figures from Zapier's pricing page:
| Tasks per month | Professional (yearly) | Professional (monthly) | Team (yearly) | Team (monthly) |
|---|---|---|---|---|
| 100 | Free plan | Free plan | n/a | n/a |
| 750 | $19.99 | $29.99 | n/a | n/a |
| 1,500 | $39 | $58.50 | n/a | n/a |
| 2,000 | $49 | $73.50 | $69 | $103.50 |
| 5,000 | $89 | $133.50 | $119 | $178.50 |
| 10,000 | $129 | $193.50 | $169 | $253.50 |
Professional is for one user. Team allows up to 25 users and adds shared app connections. Enterprise has custom pricing and limits.
What happens when you hit your Zapier task limit?
On paid plans, pay-per-task billing lets Zaps keep running after you pass your limit. Extra tasks cost 1.25x your plan's normal task rate on yearly plans and 2.5x on monthly plans, per Zapier's pricing page.
There is a ceiling. Once total usage reaches 3x your plan's limit, Zaps pause until the next billing cycle or until you upgrade. On a 750-task plan, that cap is 2,250 tasks.
Paused runs are held, not lost. Zapier's Zap limits article says you can replay held runs from Zap History once tasks are available. Replayed steps use tasks again, according to Zapier's replay article.
How do you estimate how many tasks you need?
- List every Zap that is turned on.
- For each Zap, count the action steps that call another app. Skip triggers, filters, paths and built-in tools.
- Multiply any AI steps by their multiplier (1, 3 or 5).
- Estimate runs per month from the source app, for example new leads, tickets or orders last month.
- Multiply steps by runs for each Zap, then add them up.
- Add headroom of 20 to 30% for busy months, so you are not paying overage rates.
A worked example, with illustrative volumes:
| Zap | Tasks per run | Runs per month | Tasks |
|---|---|---|---|
| Form lead to HubSpot contact, Slack alert, Asana task | 3 | 250 | 750 |
| Support ticket to Slack channel | 1 | 500 | 500 |
| AI summary of each ticket (Advanced AI) | 3 | 500 | 1,500 |
| Total | 2,750 |
A filter in front of the lead Zap drops spam before any action runs, so those runs cost nothing. Without the AI step, this team needs 1,250 tasks.
With it, 2,750. One AI step more than doubled the bill. On Team, that moves you from the 2,000-task tier ($69/mo) to the 5,000-task tier ($119/mo).
How do you use fewer Zapier tasks?
- Filter first. Filters are free, so place them right after the trigger to stop unwanted runs before any action.
- Use a native integration where one exists. Direct integrations between two apps do not use Zapier tasks. For example, Asana for Slack creates tasks from Slack messages and posts Asana rule updates to channels.
- Question every AI step. At 3x or 5x per run, AI steps add up fastest.
- Turn off Zaps nobody reads. A Slack alert into a muted channel still costs a task.
What other Zapier limits should you know about?
Tasks are not the only cap. Zapier's Zap limits page lists a few more:
- A Zap can have up to 100 steps, including steps inside paths.
- Private apps are limited to 100 requests every 60 seconds on Free and Professional, and 5,000 on Team and Enterprise.
- If 100 or more events trigger a polling Zap at once, flood protection holds them until you confirm.
- Each app also has its own rate limit, shared across every Zap in your account.
When one system makes more sense
If your task count is high because the same record is copied between a CRM, a chat tool, a task tool and a help desk, the tasks are a symptom. Keeping that record in one place removes the copying.
FitMySaaS builds one system with only the features a 10 to 40 person team uses, and our guide to software consolidation covers when that is worth it and when it is not. To see the full cost of the tools being glued together, try the SaaS cost calculator.
Questions
Do failed Zap steps use tasks?
No. Zapier does not bill a step that fails. If you replay that run later, the replayed steps do use tasks.
Is there a limit on steps in a Zap?
Yes. A Zap can have up to 100 steps, including steps inside paths. Every action step among them is a task when it runs.
Are filters free in Zapier?
Yes. Filter and Paths steps do not use tasks, so they are the cheapest way to stop a Zap from running actions it does not need.
What happens to Zaps after a downgrade?
Runs that rely on features your new plan lacks can stop. Zapier lists plan changes and ended trials among the causes of runs going on hold.