Zapier Pricing: Plans, Tasks, AI Costs, and Add-Ons

Buying path

Start with the free platform and build one representative end-to-end system before choosing a task tier. Include every successful app action, AI step, code step, and MCP call that the workflow will make in a normal period. Tables and Forms steps may be task-free, but their account limits still matter, so a useful trial measures both execution volume and the supporting data or interface footprint.

The default paid route is the individual platform subscription when production work needs multi-step workflows, premium apps, webhooks, faster polling, or paid AI features. Annual billing lowers the monthly equivalent, but the commitment is only sensible after the workflow's task rate is measured. A larger task tier should follow observed activity rather than the number of workflows on the dashboard.

Upgrade triggers

Move up when the included task pool is repeatedly exhausted or pay-per-task usage becomes normal operating spend. Task demand can rise without adding more Zaps because AI model tiers, tool calls, longer code execution, MCP calls, and specialized routing can each use more than one task. Estimate peak periods as well as the monthly average, since the overage ceiling can eventually hold further runs.

Choose the collaboration route when several builders need shared workflows, folders, app connections, permissions, and centralized sign-in. Move to an enterprise agreement when the organization needs isolated workspaces, separate workspace budgets, automated provisioning, app and action policies, advanced audit or observability, private connectivity, or contract-level support. Those are governance boundaries, not merely higher task tiers.

API and team boundaries

MCP uses the same account task pool as workflow execution, while API by Zapier runs inside eligible paid workflows. The SDK and CLI are developer-oriented beta surfaces, and embedded or sponsored automation follows separate partner terms. Do not assume that buying a core subscription creates an unlimited developer API allowance or that every programmatic surface has the same commercial status.

AI by Zapier can bill through task multipliers, and connecting an organization's own model account can add direct provider charges. Zapier Agents uses a separate activity quota, while paid Chatbots configuration has its own subscription limits. Treat those routes as independent budgets even when the same Zapier login, app connections, or Enterprise workspace can reach them.

Final pricing check

Before paying, verify the selected task tier, billing cadence, annual total, current overage rate, maximum task boundary, polling interval, included code runtime, and the account limits for Tables and Forms. Confirm which actions are task-free and test the actual model tier, tool use, retry behavior, and data volume rather than estimating from a simple two-step example.

For a team or enterprise purchase, also confirm the user limit, workspace topology, task ownership, shared connections, approval and access policies, retention, analytics, support, and invoice terms. Add the renewal and cancellation rules for every separate add-on, then keep external model, SaaS API, and embedded-automation charges outside the core Zapier plan total.