How cost grows
Zapier Tasks: what counts before you choose a plan?
Zapier generally counts successful actions rather than triggers. Multi-step workflows therefore consume Tasks according to what they do, not how tidy the Zap looks.
Count actions in the real path, including branches and repeated records.
THE BILLING ANSWER
Task pricing is workable when action volume is visible and monitored. It is less comfortable when each business event expands into many successful actions.
COST AND CONSTRAINTS
The small print, promoted to normal size
Monthly Tasks equal events × successful actions, adjusted for path mix. Check current exceptions and plan rules before contracting.
EVIDENCE
What to test before committing
Use pilot Task history, not a diagram with every arrow behaving itself.
BUILD THE EQUATION
Count what grows with use
Action depth
Count successful actions per event.
Branches
Model each likely path and repeat step.
Growth
Estimate quiet, normal and peak months.
Predictable, common-SaaS workflows with modest action depth.
High-volume processes selected from the price of the smallest plan.
SIMPLER ALTERNATIVE
Before adding another account
Reduce unnecessary downstream actions, batch records or use a native integration.
The trigger starts the work. The actions start the arithmetic.