Zapier Tasks Explained: How Many You Actually Need

Zapier’s free plan gives you 100 tasks a month. The next plan up gives you 750. Neither number means anything until you know what a task is — and most people guess wrong in the same direction, assuming one automation run equals one task.

It doesn’t. But the good news is that Zapier’s counting is unusually forgiving: several things you’d assume are billed aren’t billed at all, including the ones that fail.

Here’s the rule, then the arithmetic for three real workflows.

What Counts as a Task

Element	Cost
Trigger	Free, always
Successful action	1 task
Filter or Path step	Free
Action that errors or halts	Free
Steps skipped because a filter stopped the Zap	Free
Search step, “don’t proceed if nothing found”	Free when nothing is found
Search step, “proceed if nothing found”	1 task

Two things follow from this, and both are more generous than people expect.

Filters are free, so filter early. A filter costs nothing and prevents every step after it from running — and those skipped steps cost nothing either. Putting a filter immediately after the trigger is the single most effective way to cut task usage. There is no reason to hesitate about adding one.

Failures are free. If an action errors, it doesn’t consume a task. A Zap that breaks and fails fifty times overnight has cost you nothing but the broken automation. Worth knowing before you panic about a runaway Zap.

Zap Runs vs Tasks

These are different numbers and the distinction matters when you read your usage dashboard.

A Zap run is one trigger event — one form submission, one new row, one payment. A task is one successful action inside that run.

So a Zap with two actions, triggered ten times, is 10 runs and 20 tasks. Your plan limit is measured in tasks.

Three Workflows, Priced

A simple intake — 4 tasks per run

Form submission → create CRM record → send acknowledgement → create a task → notify your phone. The trigger is free; four actions cost four tasks. At 20 enquiries a month: 80 tasks. That fits the free plan’s 100 — except the free plan won’t let you build it, which we’ll come back to.

A filtered intake — 1 task per run, most of the time

Same workflow, but with a filter after the trigger that only continues for enquiries over a certain budget. If three of twenty submissions pass the filter, you pay for those three runs only: 12 tasks a month instead of 80. The seventeen filtered-out runs cost nothing.

That’s an 85% reduction from one free step.

A daily sync — the expensive shape

Every morning, fetch yesterday’s orders and update a spreadsheet row for each. Fifteen orders means fifteen successful actions: 15 tasks per run, about 450 a month. Zapier bills per successful action regardless of how the data arrived, so list-processing is where its costs climb too — just less steeply than Make’s operations, where every downstream module runs per item.

The Free Plan Problem

This is the part that decides whether Zapier is usable for you at all.

The free plan’s headline limit is 100 tasks a month, which sounds workable. The real limit is that Zaps are capped at two steps — one trigger, one action.

“When a form is submitted, add a row to a spreadsheet” fits. “When a form is submitted, add a row, send an email, and notify me” does not. Almost every automation in our roundup of automation tools for solopreneurs needs more than one action.

So the free plan is a way to confirm a connection works, not a way to run a business. Budget for the paid tier from the start, or start on a tool whose free plan allows multi-step workflows — which is the practical argument in our Zapier vs Make comparison.

How to Estimate Your Own Usage

1. Count the actions in each Zap. Ignore the trigger and any filters — they’re free.
2. Estimate how often it runs per month, and subtract the runs a filter will stop.
3. Multiply, then add about 20% for testing and the runs you forget about.

If a step processes a list, count one task per item rather than one per run. That’s where estimates usually break.

Four Ways to Cut Task Usage

• Filter as early as possible. It costs nothing and everything downstream of a stopped Zap is free. This is the biggest lever by a wide margin.
• Use Paths instead of separate Zaps. Path steps are free, and one Zap with branches usually costs fewer tasks than three Zaps each doing their own lookups.
• Set searches to “don’t proceed if nothing found.” That configuration costs nothing when the search comes up empty; the other one costs a task every time.
• Collapse redundant actions. Two steps writing to the same record where one update would do is one wasted task on every single run, forever.

Frequently Asked Questions

Solotimize is written by a one-person business, for one-person businesses. Recommendations are judged on what fits a solo operator’s time and budget, never on commission — and we always tell you whether we’ve used a tool or researched it. Pricing referenced above was accurate at the time of publication; always confirm current plans with the vendor.