Skip to main content
AutomationCosts
All comparisonsMake vs n8n

Make vs n8n Pricing: Credits vs Executions

Compare Make credit consumption with n8n workflow executions for the same monthly workload.
Make
Primary unit: credits
Verified 2026-09-21

Most non-AI module operations use 1 credit. Trigger and search modules normally use 1 credit per run; action modules can consume 1 credit per input bundle processed. Routers, filters and error-handler modules do not consume credits. Some AI features use dynamic rates, and Make Code uses credits based on execution time.

Pricing model Start with Make
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.

Pricing model

Some provider links on this comparison are affiliate links. AutomationCosts may earn a commission at no extra cost to you.

Key billing difference

Make usage generally scales with executed modules, while n8n Cloud meters complete workflow executions rather than individual steps.

Adding credit-consuming modules increases the baseline Make estimate, while n8n execution usage remains tied to workflow runs.
Make bundle processing, polling and dynamic-rate features can push real credit usage above a simple runs × steps estimate.
n8n execution pricing makes workflow length less important to the Cloud quota, although deployment and plan requirements still matter.
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.

10K operation workload
Cost of 10,000 Automation Operations per Month
2,000 runs · 5 steps · 4 users
Open scenario
High-volume workload
High-Volume Automation Costs
50,000 runs · 8 steps · 8 users
Open scenario