Automation · Hybrid · unit: successful tasks
Zapier pricing teardown: plan plus usage
Short answer
Zapier counts a successful action as a task (polling alone does not), and pay-per-task billing can keep workflows running above the plan quota.
Pricing mechanics
| Plan or rate | Position in ladder |
|---|---|
| Free | Entry |
| Professional | Paid step |
| Team | Paid step |
| Enterprise | Sales-led; terms by quote |
- What the docs describe
- A successful action generally counts as a task; polling alone does not. Pay-per-task billing can let workflows keep running above the plan quota.
- Free or trial fence
- Free has a monthly task quota.
- Overage or upgrade rule
- Pay-per-task billing can let workflows continue above the plan quota.
- Cap or spend control (none stated)
- Not stated in the linked pricing documentation.
A feature or configuration fence (what a plan includes) is not the same as an abuse cap. We do not infer private costs, margins or unpublished limits.
Takeaway for founders
Define the event that consumes a unit in one sentence. “Successful action, not polling” is the kind of rule buyers can check themselves.
Load into simulator
Illustrative remix · amounts and costs are editable.
Fictional tiers inspired by the pattern above. It does not reproduce Zapier's plans, invoices or margins. Fictional variable cost: $0.01 per successful task.
| Tier | Model | Price | Limit | Accounts |
|---|---|---|---|---|
| Sample entry | Flat / seat | $0 (free) | hard cap 100 successful tasks | 200 |
| Sample growth | Hybrid | $23.00 base, 1,000 successful tasks included, then $0.032 each | hard cap 9,000 successful tasks | 70 |
| Sample scale | Hybrid | $79.00 base, 6,000 successful tasks included, then $0.023 each | hard cap 45,000 successful tasks | 15 |
Related guide: Outcome-based pricing for AI support · All teardowns