Skip to main content
All comparisonsZapier vs n8n

Zapier vs n8n Pricing: Tasks vs Executions

Model the same workflow volume under Zapier task-based pricing and n8n execution-based pricing.
Zapier
Primary unit: tasks
Verified 2026-09-21

The baseline workload model assumes successful standard action steps at 1 task each. Zapier does not count triggers, Filters or Paths, failed/halted action steps, or several built-in tools as tasks. AI by Zapier can use 1x, 3x or 5x task rates depending on model tier; MCP, Lead Router and extended Code runtime can also use different rates.

n8n
Primary unit: executions
Verified 2026-09-21

A workflow execution is one workflow run, regardless of how many nodes or steps it contains. n8n states that all listed plans include unlimited users and workflows. Failed executions do not count against the Cloud execution quota; paid-plan manual editor/chat executions and sub-workflow executions are also excluded from that quota.

Key billing difference

Zapier usage usually grows with successful actions, while one n8n workflow run counts as one execution regardless of step count.

Longer workflows increase the baseline Zapier task estimate because successful billable actions are counted separately.
The same longer workflow still counts as one n8n Cloud execution per run in the baseline model.
This makes run volume and workflow complexity separate cost drivers when comparing the two billing systems.
Interactive comparison

Run the same workload through both billing models.

The calculator also keeps the third provider visible as a reference point, so differences in meter and price stay easy to separate.

Updated estimate. Zapier: 2K tasks, $69 per month, billed annually. Make: 2K credits, $9 per month, billed annually. n8n: 400 executions, €20 per month, billed annually

Example workloads
Presets change workload only. Billing mode stays as selected.
Your workload

Model monthly automation usage

Enter the workload once. We translate it into each platform's billing unit.

Billing cadence
Prices stay expressed per month for comparison; annual plans also show the full amount billed per year.
Calculator input guidance
Normalized workload
2Kstep-events / month
This uses the same normalized whole-number inputs as the pricing engine.
We do not invent unpublished tier prices. Zapier usage here assumes standard 1-task steps; AI, MCP and extended code usage can consume tasks at different rates.
Z

Zapier

tasksPublished tier fit
2Kestimated tasks/mo

5 standard-rate task-consuming steps per run

Team
$69/month
Annual billing · $828/year
2,000 tasks/month included
Verified 2026-09-21View pricing model
M

Make

creditsPublished tier fit
2Kestimated credits/mo

5 credit-consuming module actions per run

Baseline estimate only: polling trigger checks and scenarios that process multiple bundles/items can consume additional credits beyond runs × steps.
Core
$9/month
Annual billing · $108/year
10,000 credits/month included
Verified 2026-09-21Start with Make
n

n8n

executionsPublished tier fit
400estimated executions/mo

one workflow execution per run; step count does not multiply usage

Starter
€20/month
Annual billing · €240/year
2,500 executions/month included
Verified 2026-09-21View pricing model
Exact prices are shown only where a published tier matches the selected cadence and modeled workload. Provider-specific usage exceptions can still change actual consumption. Some provider links are affiliate links and may earn AutomationCosts a commission at no extra cost to you.
Usage estimates use documented billing-unit assumptions.
Published price tiers stay separate from modeled usage.
Unknown dynamic tiers remain labeled for live verification.
Related scenarios

See the same billing logic at concrete workload sizes.