How has Zapier pricing changed in 2025-2026?

Zapier pricing in 2026

Zapier continued to bill on tasks through 2025 and 2026 rather than adopting the credit or activity models several competitors moved to. A task is counted each time a Zap completes an action step that moves data; triggers, polling, filters, paths, and built-in tools such as Formatter and Delay do not consume tasks. Over-limit usage is billed automatically at roughly 1.25 times the base task rate, so Zaps keep running rather than halting.

Current plan lineup (as of July 2026)

Task allowances scale with plan size within each tier, and Zapier's product suite — Zaps, Tables, Interfaces, Chatbots, Canvas, and Agents — carries per-product allowances that differ by plan, with some products unlimited on a given tier and others capped. Zapier's official pricing page is the authoritative reference for current limits.

What changed from 2025 to 2026

• Billing model held steady. Task-based billing was retained; Zapier did not move to credits.
• AI actions reached general availability on paid plans (classify, extract, summarise, and generate steps inside Zaps). Zapier reported more than 500 million AI tasks run on the platform as of June 2026.
• Agents and Chatbots became usage-metered products alongside Zaps; their billing remains task-based rather than credit-based.
• Multi-product expansion. Tables, Interfaces, and Canvas broadened Zapier from a Zap builder into a multi-product platform, with per-product allowances that depend on plan.
• Enterprise readiness. SOC 2 Type II attestation and an MCP server, SDK, and CLI developer surface arrived in 2026.

Estimating task consumption

Because only action steps that move data consume tasks, trigger counts alone understate usage on multi-action Zaps: a Zap that fires 200 times per month and runs three action steps consumes 600 tasks. Step order matters as well — a filter placed before action steps avoids paying for actions on records that are then discarded.

Editor's Note: We manage Zapier accounts for 14 client organizations. The most common issue remains task overage — 9 of 14 clients exceeded their plan's allocation within the first three months, almost always by underestimating how many action steps their Zaps run per trigger. We recommend budgeting for 3-5x the number of workflow triggers when estimating task consumption. For clients running 5,000+ tasks per month we consistently model Make as a comparison; at that volume the difference is typically $200-$400/month in Make's favour. — Rafal Fila, ShadowGen