Task (Zapier)

A task is Zapier's unit of billing. Every plan includes a monthly task allowance, and your cost scales with how many tasks your automations consume. Understanding what does and doesn't count is the single most useful thing for keeping a Zapier bill predictable.

What counts as a task

That's the whole rule. A Zap that posts a Slack message and creates a spreadsheet row uses two tasks each time it runs. What does not consume a task:

• The trigger that starts the Zap.
• Filter and path steps that only decide whether to continue.
• Built-in tools like Formatter and Delay.

Only action steps that actually complete are metered.

A worked example

Suppose a Zap fires on every Stripe payment, filters to charges over $100, then runs two actions (Slack message + CRM update). If 1,000 payments clear that filter in a month, that's 1,000 × 2 = 2,000 tasks — even though thousands more payments triggered the Zap and were filtered out for free.

Why it matters

Because tasks scale with volume, your best sales month can become your biggest automation bill. A viral launch or a big promotion multiplies runs, and each run's actions add up fast. Teams control this by filtering early, minimizing actions per run, and moving high-volume flows onto flat-priced tools.

ChargeBell prices the Stripe-to-Slack case at a flat $24/mo with unlimited alerts on Pro — so a spike in payments changes what shows up in Slack, not what you pay.