Zapier tasks are the consumption unit that sets the price of a Zapier plan. Every plan includes a monthly task allowance, called a task tier, and the price rises with the tier.[3] Zapier defines a task as “any successful action that runs in Zapier”, and only successful actions count.[1] The pricing page announces as new that AI steps, code and the SDK “now all follow the same task-based pricing model”.[3] Catalog proof: Task; Only successful actions count as tasks.
Editions
Task tiers apply to the Professional, Team and Enterprise plans. The Free plan has a fixed 100 tasks per month. The pricing page lists tiers of 100, 750, 1,500, 2,000, 5,000, 10,000, 20,000 and 50,000 tasks, and so on up to 2 million tasks per month, plus a “Custom task limit”. Enterprise also offers “Annual task limits”.[3] Zapier states that “The higher the task tier, the lower the cost per task”.[3] Professional and Team trials have their own limits. A new account’s 14-day Pro trial has a 1,000-task limit and no pay-per-task billing.[15] Catalog proof: Pro trial is limited to 1,000 tasks without pay-per-task.
Metrics
What counts
In Zap workflows, the following count as tasks: every successful action step, successful steps in an error handler path, steps that run again in a full Zap replay, action steps inside a sub-Zap, and the Call a Sub-Zap and Return From a Sub-Zap steps. A search action set to proceed if nothing is found uses one task. If it is set not to proceed, it uses none.[1]
What does not count
“Zap triggers never use tasks.” Polling triggers check apps on a schedule, “but these polls never use tasks”.[1] The following are also free: Filter and Paths steps, steps that error or halt, steps skipped by an earlier condition, the Start a Sub-Zap trigger, steps for Zapier Tables and Zapier Forms, and the Formatter, Delay, Looping, Sub-Zap, Digest, Zapier Manager and Storage apps.[1] Most of these exemptions date from the January 2024 plan changes, which removed Filter, Formatter and Paths from task counting for accounts on current plans.[7] Catalog proof: Triggers and polling never use tasks; Built-in Zapier tools and Tables and Forms steps are task-free.
Product conversion rates
Some products convert their work into tasks at their own rates.
| Product | Rate | Catalog row |
|---|---|---|
| Zapier MCP | 2 tasks per successful tool call; failed calls free[6] | MCP tool call |
| Zapier Lead Router | 5 tasks per successful lead routed[1] | Lead routed |
| AI by Zapier | Model rate of 1x, 3x or 5x per run, plus the same rate per tool call[4] | AI by Zapier model tier multiplier |
| Code by Zapier | 1 task per run, plus 1 task per extra 30 seconds over standard runtime[5] | Code by Zapier extended runtime block |
| Zapier SDK | Free while in beta[3] | none |
AI by Zapier (2026-10-01). The formula is “Tasks used per run = (1 × model rate) + (number of tool calls × model rate)”. The Standard tier is 1x, Advanced 3x and Premium 5x, and a step that uses the customer’s own AI account is 1x.[4] For example, a Premium step that makes two tool calls uses 15 tasks. New steps on paid plans default to Premium, so AI steps can use five times more tasks than expected unless the tier is changed. Each step also has a per-run task limit. It is 75 tasks by default, can be raised to 500, and pauses the step for approval when reached.[4] Catalog proof: AI by Zapier tasks follow the model tier formula; New AI by Zapier steps default to the Premium tier; AI by Zapier per-run task limit.
Code by Zapier (2026-06-15). Standard runtime is 1 second on Free, 30 seconds on Professional and Team, and 2 minutes on Enterprise. Code that runs longer is charged 1 task per extra 30 seconds, and “Partial blocks round up”. Free plan steps that run longer than 1 second fail.[5] Catalog proof: Code by Zapier extended runtime is billed per 30 seconds.
Zapier MCP (2026-09-08). Zapier MCP “runs on your existing Zapier plan, with no separate billing”. Because each successful call uses two tasks, a request that repeats an action many times uses proportionally more of the allowance.[6] Catalog proof: Zapier MCP tool calls use two tasks each.
Counting / floors
Pooling and reset. Tasks are shared across the account. Zap workflows, AI steps, code, MCP and the SDK all draw from one allocation.[3] Code by Zapier tasks reset on the billing date each month.[5] An annual plan still has a monthly task limit. The pricing page lists task tiers “per month” and offers annual task limits as an Enterprise feature.[3]
At the limit, with pay-per-task (2026-08-15). “If you exceed your plan’s task limit, you’ll automatically switch to pay-per-task billing for the remainder of your pay period”. The rate depends on the plan and billing cycle and is shown in billing settings.[2] The pricing page says pay-per-task usage “is charged at a higher per-task rate than your base subscription tasks”.[3] When the feature launched in January 2024, Zapier announced a rate of “1.25x the cost of a task on your plan”. The current articles do not restate that figure.[7] Catalog proof: Pay-per-task rate at launch was 1.25x the plan task cost.
The 3x ceiling. Pay-per-task usage stops at a maximum “set at 3 times your plan’s task limit, which includes your plan allocation and optional pay-per-task usage”. On a Professional 750 plan, the account can therefore use 750 plan tasks plus 1,500 pay-per-task tasks, 2,250 in total, before Zap workflows stop until the next period.[2] Zapier sends emails at 80% and 100% of the pay-per-task limit.[1] Catalog proof: Pay-per-task usage is capped at three times the plan task limit.
At the limit, without pay-per-task. If the plan does not include pay-per-task billing, or the feature is switched off, Zapier “will hold any new Zap runs until your billing cycle resets”. Held runs can be replayed after a reset, an upgrade or enabling pay-per-task billing.[1] Catalog proof: Without pay-per-task, Zap runs are held at the task limit.
Who controls overage. Pay-per-task billing is enabled by default for accounts that joined after January 2024. On Professional and Team, only the account owner can switch it off. Enterprise accounts created after June 2025 must contact their account manager to disable it. Usage accrued before it is switched off is added to the next invoice.[2] Catalog proof: Pay-per-task billing is on by default for newer accounts.
Discounts. The 15% non-profit discount applies to plans but not to pay-per-task charges.[14] Catalog proof: Non-profit discount excludes pay-per-task charges.
Plan changes and the task count
When a customer upgrades, the account’s billing date and task count reset, the remaining time on the old plan is credited per day, and any pay-per-task usage to date is charged at once. Downgrades take effect at the end of the billing cycle. A downgrade is scheduled only when checkout is completed.[8] A lower tier “may” cause runs to be held if workflows use more tasks than the new plan allows.[8] Catalog proof: Upgrades are immediate, prorated and reset the billing date; Downgrades take effect at the end of the billing cycle.
Virtualization & partitioning
Not applicable to tasks. Enterprise organizations can allocate tasks by workspace. A workspace with no limit keeps running into pay-per-task billing, while a workspace with a limit is held when it reaches that limit. “If the sum of your workspace(s) task limits exceeds the organization plan limit, Zapier will charge your organization for overages.”[9] Catalog proof: Organization and workspace task limits; Workspace limits above the plan limit create overage.
Cloud / BYOL
Not applicable. The only bring-your-own option is an AI provider key for AI by Zapier, charged at the 1x rate. Calls to the provider are billed separately by that provider.[4]
Usage reporting
Zapier shows task usage in several places. The billing page “captures total task usage across all products and access methods, and is always the most accurate figure for your account”. The Zap history Task usage tab excludes MCP usage.[10] Team and Enterprise admins can export a CSV with each member’s tasks, Zaps and app connections, but only for the current billing cycle.[11] Enterprise admins can set an hourly task threshold, which Zapier checks every 15 minutes.[12] Zapier’s own sizing advice is to multiply the number of actions per run by the expected number of runs. For example, a three-action Zap triggered by 10 leads a day uses about 900 tasks a month.[13] Catalog proof: Billing page is the authoritative task usage figure; Team and Enterprise admins can export per-member task usage; Enterprise task usage alerts are checked every 15 minutes.
Because the member export covers only the current cycle, an organisation that wants a history of consumption, for chargeback or for choosing a renewal tier, has to save the export every cycle.
Out of scope
- Zapier Agents activities, which are a separate quota. See Zapier Agents, Chatbots, Tables, Forms and MCP limits.
- Exact per-tier prices and pay-per-task rates. Zapier shows these in the price selector and in each account’s billing settings, not in a static price list.[2]
- Time-limited promotions that make particular apps task-free.