All toolsn8n usage tool
n8n Execution Calculator
n8n prices hosted plans around complete workflow executions rather than multiplying usage by every step inside the workflow. That makes run volume the main baseline input for execution count.
Baseline formula
Monthly completed workflow runs = estimated n8n executions
Example
8,000 completed workflow runs model about 8,000 n8n executions whether each workflow has 3 steps or 30.
Interactive calculator
Enter your workload and compare the modeled usage.
The same calculator keeps all three providers visible so the billing-unit difference stays explicit.
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
Billing cadence
Prices stay expressed per month for comparison; annual plans also show the full amount billed per year.
Calculator input guidance
Normalized workload
2K
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 fit2K
Team
$69
Annual billing · $828/year
2,000 tasks/month included
Verified 2026-09-21View pricing model
M
Make
creditsPublished tier fit2K
Baseline estimate only: polling trigger checks and scenarios that process multiple bundles/items can consume additional credits beyond runs × steps.
Core
$9
Annual billing · $108/year
10,000 credits/month included
Verified 2026-09-21Start with Make
n
n8n
executionsPublished tier fit400
Starter
€20
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.
Guidance
What to count — and what not to count.
Use completed workflow run volume as the baseline execution count.
Do not multiply executions by the number of nodes or processing steps.
Keep Cloud and self-hosted pricing separate; a larger self-hosted plan is not automatically a Cloud upgrade.
When a Cloud workload exceeds the exact published tiers stored here, verify the current live plan instead of extrapolating a price.