Zapier Tasks, Make Credits and n8n Executions: What Each One Counts

Zapier counts successful actions

Zapier's help center defines a task as any successful action that runs in Zapier, and says only successful actions count toward task usage.

Several things never count: trigger steps, any Filter or Paths step, action steps that error or halt, and steps that use Formatter, Delay, Looping, Sub-Zap, Digest, Zapier Manager or Storage.

Zapier's own example is a three-step Zap that takes a Gmail trigger, uploads a file to Dropbox and posts a Slack message. It uses two tasks per run, because only the two action steps count. Ten runs is twenty tasks.

Make counts credits, and most actions cost one

Make bills in credits. Its help center says that for non-AI apps and third-party AI services, “1 operation equals 1 credit”. In practice an ordinary module action costs one credit.

AI features are the exception. Make says some modules use credits based on “actual usage rather than a fixed rate”, mainly token consumption, and that some modules with fixed usage cost more than the default one credit. Make tags those modules.

If you used Make before the change, the help center says existing operations were converted to credits at a 1 to 1 ratio, and that plan pricing, including the cost of buying credits, stayed the same.

Articles that describe Make as billing per operation predate that change. So did earlier versions of our own Make and Zapier guides, which we have corrected.

n8n Cloud counts workflow executions

n8n Cloud pricing is based on monthly workflow executions. n8n defines an execution as a single run of your entire workflow, and says it does not matter how many steps the workflow has or how much data it processes. It is still one execution.

Self-hosting works on different terms. n8n's pricing page lists a self-hosted Community Edition, and self-hosted Business and Enterprise plans that use license keys. Check the plan terms for how those are billed.

The same three questions, answered for each

One workflow, three bills

Take a workflow that starts on a new form submission and then runs five action steps: look up the contact, create a CRM record, post to Slack, add a spreadsheet row and send a confirmation email. Assume 1,000 submissions a month and no failures.

• Zapier: the trigger is free and the five actions count, so 5 tasks per run and 5,000 tasks a month.
• Make: five module actions at one credit each is about 5 credits per run and about 5,000 credits a month, plus whatever the trigger costs and any AI modules. Check the credit rules for the modules you use.
• n8n Cloud: 1,000 executions a month, whatever the number of steps.

What this changes in practice

The figures above are an illustration, not a quote. They show the shape of the difference. Add ten more steps to the workflow and Zapier and Make each count about ten more units per run, while n8n Cloud still counts one execution. With a single action per run the gap disappears, because one task, one credit and one execution are the same size.

• On Zapier, put filters straight after the trigger. Triggers and Filter steps are free, and steps after a failed filter do not run, so a record that fails the filter costs no tasks.
• Count steps per run before you compare plans. Runs per month multiplied by steps per run is the figure that lines up across all three.
• On Make, look up the credit rules for the modules you use. AI modules can cost more than one credit, and the cost varies with usage.
• Treat older comparisons with suspicion. Any article that says Make bills per operation was written before credits.

Where price stops being the deciding factor

Usage counting is one input. Logic, maintenance and hosting decide the choice more often, and our Zapier alternatives and Make vs Zapier guides cover those.