Zapier is still easy to start and surprisingly easy to under-budget. The Free plan includes 100 tasks a month. Professional starts at $19.99 per month when paid yearly, while Team starts at $69 per month when paid yearly; Enterprise is custom-priced. Paying monthly costs more, and Zapier currently advertises a 33% saving for yearly billing.
For most small businesses, the right answer is Professional if one person owns the automations and Team only when several people need shared workflows, app connections, folders, and governance. The subscription price is only the floor. Real cost depends on how many successful actions run, which features those actions use, whether pay-per-task billing is enabled, and whether separate products such as Zapier Agents are part of the stack.
Pricing verified: August 20, 2026, in USD against Zapier's public pricing and help documentation. Prices can vary by task tier, currency, taxes, and contract. This is vendor-document-verified editorial analysis, not hands-on testing. No Search Console or GA4 evidence was available or used.
A Zapier budget starts with workflow volume, but every successful billable step determines how quickly the task pool disappears.
How much does Zapier cost in 2026?
Zapier has four main automation plans: Free, Professional, Team, and Enterprise. Free is a genuine starter tier; Professional removes the main workflow restrictions; Team adds collaboration and administration; Enterprise adds organization-level controls and contracting.
| Plan | Public starting price (USD) | Entry task allowance | Users | Best fit |
|---|---|---|---|---|
| Free | $0 | 100 tasks/month | 1 | Testing simple two-step Zaps |
| Professional | $19.99/month, paid yearly | 750 tasks/month at the public starting tier | 1 | Solo owner or automation operator |
| Team | $69/month, paid yearly | Selectable paid task tiers | Up to 25 | Shared automation ownership |
| Enterprise | Custom | Custom/annual task limits | Unlimited | Central governance, security, and scale |
Professional includes multi-step Zaps, unlimited premium apps, webhooks, AI fields, and conditional form logic. Team adds shared Zaps and folders, shared app connections, SAML SSO, priority support, and up to 25 users. Enterprise adds unlimited users, advanced admin permissions, app controls, deployment options, observability, annual task limits, and potentially a Technical Account Manager depending on the contract or threshold.
The advertised Professional and Team amounts are starting prices, not universal flat fees. Choosing a larger task allowance raises the subscription. Zapier exposes tiers from hundreds of tasks per month into the millions, and Enterprise can use custom limits.
Is annual Zapier billing cheaper than monthly billing?
Yes. Zapier's pricing page currently says yearly billing saves 33% compared with monthly billing. The displayed $19.99 Professional and $69 Team starting prices are monthly equivalents under yearly billing, meaning the customer commits to and pays for an annual term.
Monthly billing is better when the workload is unproven or seasonal because the business retains an easier exit. Annual billing is usually better once task demand has been measured for at least two or three billing cycles. Saving on the base plan and then repeatedly paying for excess tasks is not much of a saving; it is merely a cheaper entrance to an expensive room.
Before committing annually, record:
- monthly successful task usage, including the busiest month;
- tasks per completed business event;
- workflows that use higher-rate AI, MCP, or Lead Router steps;
- expected growth and seasonal peaks;
- whether more than one person needs to edit or own automations.
What counts as a Zapier task?
A task is generally a successful unit of work completed by Zapier, but the 2026 rate card makes the exact step type important. A normal app action costs one task. Triggers do not consume tasks, and many built-in tools consume zero.
The trigger starts the workflow for free; successful billable actions consume the task pool.
| Workflow activity | Current task rate |
|---|---|
| Trigger, including a polling trigger | 0 |
| Standard successful app action | 1 per step |
| Formatter, Paths, Filters, Delay, Looping, Sub-Zaps, Digests, Storage, Zapier Tables and Forms | 0 |
| Code by Zapier step within its plan runtime allowance | 1 |
| Extended Code runtime | 1 per additional 30 seconds beyond the allowance |
| Lead Router step | 5 |
| Zapier MCP tool call | 2 |
| AI by Zapier standard model step | 1, with no tool calls on that tier |
| AI by Zapier advanced model step or tool call | 3 |
| AI by Zapier premium model step or tool call | 5 |
Only successful actions count in ordinary Zaps. Failed actions do not. A trigger can poll an app thousands of times without consuming tasks; tasks are used only when new data is found and downstream billable actions succeed.
For example, suppose a new lead triggers a Zap that creates a CRM contact, sends an email, posts a team alert, and creates a follow-up task. That is four tasks per lead, not one. At 100 leads a month, the workflow uses about 400 tasks. Add another successful billable action and usage rises to 500.
Do polling intervals change the Zapier bill?
Polling speed changes latency, not task consumption by itself. Zapier lists a 15-minute polling interval on Free, two minutes on Professional, and one minute on Team and Enterprise. An instant trigger can run faster where the connected app supports it.
Zapier's own example explains that checking Facebook every two minutes does not consume tasks for the checks. If two new leads are found and successfully sent to a CRM, two tasks are consumed. This distinction matters: paying for a faster plan can improve response time, but the faster polling frequency does not automatically create a larger bill.
Which features force a move beyond Free?
Free works for experiments, not a mature small-business automation system. Its 100-task allowance, one user, two-step Zaps, and 15-minute polling make it easy to prove a concept but restrictive once a workflow needs several actions.
Professional is the practical minimum when the business needs any of the following:
- more than one action after a trigger;
- premium apps;
- webhooks;
- faster two-minute polling;
- custom logic across multi-step Zaps;
- a task allowance above 100 per month.
Team is not primarily a faster Professional plan. It is the collaboration and control tier. Move to Team when multiple people need shared app connections, shared folders and workflows, permissions, SAML SSO, or priority support. Do not pay $69 simply because task usage is growing; first compare a larger Professional task tier unless collaboration is the actual problem.
Enterprise becomes relevant when unlimited users, provisioning, domain controls, action restrictions, custom retention, observability, static IP options, or centralized governance are procurement requirements.
What happens when Zapier runs out of tasks?
When a paid account reaches its included task limit, Zapier can charge separately for additional tasks through pay-per-task billing. Zapier emails the account when included usage is exhausted, again at 80% of the pay-per-task allowance, and at 100% of that allowance.
The pay-per-task ceiling is currently equivalent to three times the selected plan's included task limit. Once that ceiling is reached, additional tasks are held until the billing cycle resets. The account can also upgrade and replay held runs.
If pay-per-task billing is unavailable or switched off, new Zap runs are held after the included task limit is reached. This is safer for cost control but can quietly interrupt lead routing, customer notifications, invoicing, or other operational workflows.
Zapier does not publish one simple universal overage dollar rate on the public plan card because pricing depends on the selected plan and task tier. The honest budgeting method is to check the account's pay-per-task rate before enabling it and compare that rate with the next task tier. If normal usage repeatedly exceeds the allowance, upgrading is usually more predictable than treating overage as permanent capacity.
What is the real monthly cost for a small business?
Real monthly cost is the subscription plus excess usage, add-ons, external AI/API fees, and the labour required to build and maintain the workflows. The scenarios below isolate ordinary Zap automation and use transparent workload assumptions; they are not customer benchmarks.
| Scenario | Workload assumption | Estimated ordinary tasks/month | Likely fit | Base subscription posture |
|---|---|---|---|---|
| Light | 60 leads × 3 actions, plus 40 admin events × 2 actions | 260 | Professional | Starts at $19.99/month paid yearly; entry 750-task tier has headroom |
| Moderate | 250 leads × 4 actions, plus 150 order/admin events × 3 actions | 1,450 | Professional at a larger task tier | Price rises above the advertised starting amount; select at least 1,500 tasks and preferably keep buffer |
| Higher volume | 800 mixed events × average 4 actions | 3,200 | Professional or Team at 5,000 tasks | Choose Team for shared ownership/governance, not merely for volume |
Light automation: about 260 tasks a month
A solo service business captures leads, creates contacts, sends acknowledgements, and creates follow-up tasks. With 260 expected tasks, the Professional starting tier's 750-task allowance leaves substantial room for retries, extra actions, and growth. The public annual-billing equivalent starts at $19.99 a month, or about $239.88 across a year before tax.
Moderate automation: about 1,450 tasks a month
A busier company combines lead handling with order or project administration. At roughly 1,450 tasks, the 750-task entry tier is too small. The company should select at least the 1,500-task tier, though that leaves almost no buffer. A 2,000-task tier is operationally safer if the extra subscription cost is lower than likely pay-per-task charges.
Higher-volume automation: about 3,200 tasks a month
A scaling business with roughly 800 monthly events and four billable actions per event needs about 3,200 tasks. A 5,000-task tier creates useful headroom. One automation owner can still use Professional; a multi-person operations function should consider Team for shared connections, permissions, and recovery when the original builder is absent.
The main lesson is simple: count successful actions, not Zaps. Ten busy Zaps can cost more than a hundred rarely used ones.
Are Zapier Agents and other AI products included in these costs?
No. Ordinary Zap task economics should be separated from Zapier Agents activity and from other separately priced AI products. Zapier's public pricing currently shows Agents Free with 400 activities per month and Agents Pro at $33.33 per month when $400 is billed annually, including 1,500 activities per month. Agents Enterprise is custom-priced.
An Agent activity is not the same billing unit as a standard Zap task. Likewise, AI by Zapier steps embedded inside a Zap can cost one, three, or five tasks per model step and per supported tool call, depending on model tier. Zapier MCP uses two tasks per successful tool call. External model charges can also apply when using a bring-your-own-model arrangement.
Budget these as separate lines:
- Zap automation subscription and task tier.
- Pay-per-task charges, if enabled.
- Zapier Agents plan and activity allowance.
- AI by Zapier task multipliers inside ordinary workflows.
- External AI provider or connected-app fees.
- Build, monitoring, and maintenance time.
Combining all of them into a vague “Zapier costs $20” claim is how a cheap automation experiment becomes an accounting jump scare.
Which Zapier plan should you choose?
Choose based on workflow ownership first and task volume second. Volume determines the task tier; ownership and governance determine the plan family.
Solo ownership, team collaboration, agency separation, and scaling governance lead to different plan requirements.
Solo owner: Professional
Professional is the default verdict for a solo owner running real business workflows. It unlocks multi-step Zaps, premium apps, webhooks, and faster polling without paying for team controls. Free is suitable only while proving a workflow under 100 tasks.
Small operations team: Team
Team is appropriate when several employees must build, edit, troubleshoot, or own automation. Shared app connections and folders reduce dependence on one employee's account. If only one operator builds everything, use Professional with the right task tier until collaboration becomes necessary.
Agency: Team, with client separation planned carefully
An agency should usually use Team because shared ownership, folders, and connections matter more than raw task volume. However, confirm how client credentials, billing, offboarding, and permissions will be isolated before centralizing client automations. Enterprise may be justified for stricter access controls or large client environments.
Scaling SMB: Team first, Enterprise when governance becomes mandatory
A scaling SMB should start with Team if 25 users, shared connections, SSO, and priority support cover the requirement. Enterprise is the fit when unlimited users, SCIM, domain capture, custom retention, app/action restrictions, observability, or formal procurement support are mandatory—not merely because the task count is high.
How can a small business control Zapier costs?
The best cost control is designing and monitoring task-efficient workflows before a spike occurs.
- Review task usage by Zap every month.
- Forecast events multiplied by billable actions, then add 20% to 30% headroom.
- Use zero-task built-in tools such as Filters, Paths, Formatter, and Tables where they genuinely replace billable actions.
- Remove redundant downstream steps and duplicate automations.
- Treat AI steps, MCP calls, Lead Router, and extended Code runtime as different rate classes.
- Set task alerts where the plan supports them.
- Decide deliberately whether pay-per-task billing or held runs are the safer failure mode.
- Reprice the next task tier whenever overage becomes recurring.
- Keep a workflow owner and an operational fallback for critical processes.
Is Zapier worth the price for a small business?
Zapier is worth the price when it replaces repetitive cross-app work without creating an unowned web of fragile workflows. Professional remains the strongest fit for a solo operator; Team earns its premium through collaboration and governance, not simply more automation.
The bad fit is a business that cannot estimate event volume, does not monitor tasks, and treats every workflow as “set and forget.” Zapier's interface makes automation approachable, but approachable is not the same as costless. Model the task math, keep ordinary Zaps separate from agent and AI usage, and select a tier with enough headroom to avoid turning overage into the monthly plan.
Zapier pricing FAQs
Does a Zapier trigger count as a task?
No. Zap triggers, including polling checks, do not consume tasks. Successful downstream billable actions do.
Do Filters and Paths count as tasks?
Zapier's current task-rate page lists Filters, Paths, Formatter, Delay, Looping, Sub-Zaps, Digests, Storage, Tables, and Forms as zero-task built-in tools.
Can Zapier stop workflows when the task limit is reached?
Yes. If pay-per-task billing is off or unavailable, Zapier holds new runs after the included task allowance is exhausted. With pay-per-task enabled, overage can continue until the current pay-per-task ceiling is reached.
Does Team include unlimited tasks?
No. Team adds collaboration and administration, but task allowances still depend on the selected tier.
Are Zapier Agents activities the same as Zap tasks?
No. Zapier Agents uses activities and has separate plan limits. AI by Zapier steps and MCP calls also have their own task rates within the broader Zapier platform.
Should a small business pay yearly?
Pay yearly after measuring stable usage and confirming the required task tier. Use monthly billing while volume, workflow design, or product fit is still uncertain.