What is a Zapier Task? Pricing Explained
If you are evaluating Zapier, the most important thing to understand is how tasks work. Zapier does not charge per Zap or per user on most plans. It charges per task. A task is one successful action step inside a Zap. Getting this wrong means underestimating your costs, hitting limits mid-month, and having all your automations paused at the worst possible time. This guide explains exactly how tasks are counted, what is free, and how to estimate your monthly usage.
The Simple Definition
A task = one successful action step in a Zap.
Triggers do not count. Filters do not count. Searches do not count (unless they are followed by a create action). Only the action steps that actually execute and succeed are billed as tasks.
This is the billing unit that determines your monthly cost on every Zapier plan. The Free plan includes 100 tasks per month. Starter gives you 750. Professional gives you 2,000. Team also gives 2,000 (shared across the workspace). Enterprise negotiates a custom volume.
The number of Zaps you create is separate from the number of tasks you consume. You could have one Zap that uses 1,500 tasks per month, or fifty Zaps that collectively use 200 tasks. It is the total task count that matters, not how many workflows you have running.
Visual Examples: How Tasks Are Counted
Example 1: Single-step Zap
Result: 1 task per run
The trigger is free. The single action step counts as 1 task. If this Zap runs 50 times per month, it uses 50 tasks.
Example 2: Multi-step Zap (3 actions)
Result: 3 tasks per run
The trigger is free. Each of the 3 action steps counts as 1 task. If this Zap runs 100 times per month, it uses 300 tasks.
Example 3: Zap with a Filter
Result: 2 tasks per run (when the filter passes)
The filter itself is free. If an order is under $100, the filter stops the Zap and zero tasks are used. If the order is over $100, both actions run and 2 tasks are consumed. Filters save you tasks by preventing unnecessary actions.
Example 4: Zap with Paths (branching)
Path A: High priority
Page on-call (1 task) + Create Jira (1 task)
Path B: Low priority
Add to backlog (1 task)
Result: 2 tasks (Path A) or 1 task (Path B)
Only the actions in the matched path execute. If a high-priority ticket comes in, both actions in Path A run (2 tasks). If it is low priority, only Path B runs (1 task). Paths do not multiply your tasks; they route to the appropriate branch.
How Many Tasks Do I Need?
To estimate your monthly task usage, multiply the number of action steps in each Zap by how many times that Zap runs per month. Add up the totals across all your Zaps. Here is a quick reference.
| Zap Type | Actions | Runs/mo | Tasks/mo |
|---|---|---|---|
| Email to spreadsheet | 1 | 200 | 200 |
| Form to CRM + email | 2 | 150 | 300 |
| Order processing (4 steps) | 4 | 100 | 400 |
| Lead routing with paths | 2 avg | 300 | 600 |
| Content publishing (5 steps) | 5 | 12 | 60 |
Quick formula: Tasks per month = (number of action steps in Zap) x (times the Zap runs per month). Add up all your Zaps to get your total. If you use filters, your actual usage will be lower because filtered-out runs consume zero tasks.
What Counts as a Task (and What Does Not)
Counts as a task
- Creating a row in Google Sheets
- Sending an email via Gmail or Mailchimp
- Creating a record in Salesforce or HubSpot
- Posting a message to Slack
- Updating a Trello card or Asana task
- Any action step that completes successfully
Does NOT count as a task
- The trigger that starts the Zap
- Filter steps that evaluate conditions
- Formatter steps that transform data
- Failed action steps (errors, timeouts)
- Zap runs stopped by a filter
- Searching for a record (without creating)
Important caveat about Formatter
Zapier's Formatter step (which lets you reformat dates, text, numbers, etc.) is technically a built-in action but does not count as a task. However, some built-in Zapier utilities like "Looping" can generate multiple task-consuming actions per run. Always check Zapier's current documentation on which built-in steps are task-free.
How to Reduce Your Task Usage
Use Filters to block unnecessary runs
Add a Filter step early in your Zap to prevent actions from running on irrelevant triggers. For example, if your Zap processes new Shopify orders, add a filter to only continue for orders above a certain value. Every filtered-out run costs zero tasks. This is the single most effective way to lower your task count.
Consolidate steps with Paths
Instead of creating multiple Zaps for different conditions (each with their own trigger and actions), use a single Zap with Paths. Paths route to different branches based on conditions, so only the relevant actions run. One Zap with Paths uses fewer total tasks than three separate Zaps triggered by the same event.
Reduce action steps per Zap
Each action step costs one task. If a Zap has 5 actions and runs 200 times per month, that is 1,000 tasks. Can you eliminate one step? Maybe the Slack notification is redundant because your team already gets email alerts. Cutting one step from a 5-step Zap saves 200 tasks per month.
Use webhooks instead of polling triggers
Polling triggers check for new data at fixed intervals (every 1, 2, or 15 minutes depending on your plan). This can cause duplicate triggers or missed events. Webhook triggers fire instantly when data changes, which means fewer erroneous runs and more predictable task usage. Webhooks require the Professional plan or higher.
Audit your Zaps monthly
Check your Zapier dashboard at Settings then Usage to see which Zaps consume the most tasks. Look for Zaps that run frequently but produce low value. Turn off or optimize the top consumers. A monthly 10-minute audit can prevent surprise overages.
Task Limits by Plan
Free
100
tasks/mo
$0/mo
Starter
750
tasks/mo
$29.99/mo
Professional
2,000
tasks/mo
$73.50/mo
Team
2,000
tasks/mo
$103.50/mo
Enterprise
Custom
tasks/mo
Custom/mo
Prices shown are for annual billing. Monthly billing costs 30-40% more on every paid tier. All paid plans allow purchasing additional task packs if you exceed your monthly limit.
Common Mistakes When Estimating Tasks
Confusing Zaps with tasks
The number of Zaps you have is not the same as the number of tasks you use. One Zap with 5 actions running 200 times uses 1,000 tasks. Five single-step Zaps running 10 times each use only 50 tasks. Always calculate based on actions times runs, not Zap count.
Forgetting that multi-step Zaps multiply
A 4-step Zap does not use 1 task per run. It uses 4 tasks per run (one per action step). This catches many first-time users off guard. If you have a 5-step Zap running 400 times per month, that alone consumes your entire Professional plan allowance of 2,000 tasks.
Not accounting for growth
If your business processes 100 orders per month today and your Zap uses 3 tasks per order (300 tasks), that fits comfortably in the Starter plan. But if orders double to 200 next quarter (600 tasks), you are now approaching the limit. Always plan for 6-12 months of growth, not just current volume.
Frequently Asked Questions
Do triggers count as tasks?
Do filters count as tasks?
Do failed tasks count toward my limit?
What happens when I run out of tasks?
Can I buy additional tasks without upgrading my plan?
Ready to compare Zapier plans?
Now that you understand how tasks work, compare plans side by side to find the right fit for your workflow volume and feature needs.