n8n Cloud pricing: understanding the billing model and picking your plan (2026)

"How much does n8n Cloud cost?" is probably the most poorly framed question in the n8n ecosystem — not because the amounts are secret, but because the real question lies elsewhere: how does n8n count what you consume, and how does that counting model compare to Zapier or Make once your workflows involve AI? This guide breaks down n8n Cloud's billing model, the logic behind the Starter, Pro and Enterprise plans, the method for estimating your real volume before subscribing, and the point at which self-hosting becomes the rational option again. Deliberately, you will find no specific amounts here: the pricing grids change regularly, and the only reliable source is the official n8n.io/pricing page.

The key principle: n8n bills per execution, not per task

n8n Cloud's entire pricing logic fits in one definition: one execution = one full pass through the workflow, from the trigger to the last node. Whether a workflow contains 3 nodes or 60, whether it calls an AI model once or twelve times, whether it loops over 200 rows of a Google Sheet — that counts as a single execution against your monthly quota.

That is the exact opposite of the dominant model among competitors. Zapier counts every task (each action executed inside a Zap), Make counts every operation (each module traversed, multiplied by the number of items processed). On a simple two-step scenario, the difference is anecdotal. On a typical AI workflow — incoming webhook, enrichment, LLM call, parsing, CRM update, Slack notification, logging — a single trigger burns six or seven tasks on Zapier, one single execution on n8n. Multiply that by hundreds of triggers per day and the gap becomes structural, not marginal. This is the central argument of our n8n vs Make vs Zapier comparison, and the reason many teams end up migrating from Zapier to n8n once their automations get more complex.

The practical consequence: on n8n Cloud, making a workflow more sophisticated costs nothing extra. Adding a validation node, a retry step, a second AI call to double-check the output of the first — your bill does not move. This decoupling between workflow richness and cost is especially valuable for AI agents, which naturally chain many steps together.

Starter, Pro, Enterprise: what actually varies between the plans

n8n Cloud's three plans share the same engine and the same nodes. What sets them apart is not crippled automation features, but capacities:

• Monthly execution volume: the central quota, the one you need to estimate before choosing (see next section);
• Number of concurrent executions: how many workflows can run at the same time. Barely noticeable at first, this ceiling becomes critical when webhooks arrive in bursts or when slow AI workflows (30 to 60 seconds per run) start stacking up;
• Number of active workflows: workflows triggered automatically (schedule, webhook) count, manually launched workflows do not;
• Execution history retention: essential for debugging a workflow that failed several days ago;
• Team and enterprise features: shared projects, granular roles and permissions, SSO/SAML, environment variables, priority support — concentrated on Pro and above all Enterprise, the latter adding compliance requirements and the option of a dedicated deployment.

Once again: the precise quotas and amounts attached to each plan change with every pricing update. Do not make a decision based on a screenshot seen in a 2024 article — check the current grid on n8n.io/pricing.

Estimating your real execution volume before subscribing

The classic mistake is picking a plan on gut feeling, then discovering a blown quota at the end of the month — or, conversely, an oversized plan. The method is simple: list your planned workflows and, for each one, work out the number of monthly triggers.

• Scheduled workflows (Schedule Trigger): the math is deterministic. A workflow running every 15 minutes means 4 × 24 × 30 ≈ 2,880 executions per month — even if it finds nothing to process most of the time. A thrifty reflex: stretch the interval of polls that usually come back empty, or replace a frequent poll with a webhook whenever the source application allows it;
• Event-driven workflows (Webhook, Chat Trigger, inbound email): volume follows your actual activity. Base it on your existing metrics (orders/month, leads/month, messages/month) rather than intuition;
• Sub-workflows: a workflow called by another via Execute Workflow counts too — a pipeline heavily split into sub-workflows consumes more executions than an equivalent monolith, something to weigh in your architecture;
• Error margin: add 20 to 30% for retries, testing and growth, then monitor actual consumption during the first month in the dashboard.

What the subscription does not cover: your AI API calls

A point often discovered too late: n8n Cloud bills the orchestration, not the intelligence. Every call to OpenAI, Anthropic, Mistral or any other provider goes through your own API keys and is billed to you separately, per token. An AI agent workflow running 1,000 times a month can therefore cost more in tokens than in n8n subscription — especially if the prompt carries a long context on every turn. Budget the two lines separately, and equip yourself to track the second one: our guide to tracking the cost of AI calls in n8n shows how to log token consumption workflow by workflow, before the provider's invoice becomes your alerting system.

When self-hosting becomes the rational option

Since n8n is source-available, the alternative to Cloud is hosting it yourself — with executions then unlimited, within the capacity of your server. The switch becomes rational in three situations: high, predictable volume (tens of thousands of monthly executions make the cloud quota structurally uncomfortable), sensitive data that must not transit through third-party infrastructure (healthcare, legal, HR), or a need for fine-grained control (pinned version, community nodes, memory tuning, queue mode with Redis to scale AI workflows).

But self-hosting is not free either: it shifts the cost from the subscription to the server and, above all, to human time — installation, updates, backups, monitoring, incident recovery. That hidden cost is systematically underestimated; we quantified it in detail in our analysis of the real cost of self-hosted n8n, and the full self-hosted vs Cloud comparison helps you decide based on your profile.

This tension between renting and owning is nothing new. The landmark paper by Armbrust and co-authors (Berkeley), "A View of Cloud Computing", published in 2010 in Communications of the ACM (Google Scholar page), formalizes what the cloud actually sells: elasticity (paying as you go rather than provisioning for the peak) and the transfer of the risk of over- or under-provisioning to the provider. Applied to n8n: if your execution volume is irregular or growing unpredictably, the Cloud absorbs that risk for you; if it is massive and stable, you are paying an elasticity premium you no longer need — and owning the infrastructure makes sense again.

A five-question decision checklist

1. How many executions per month? Do the math trigger by trigger (section above), not by instinct;
2. Are your AI workflows slow? If so, look at the concurrent execution ceiling as much as the monthly quota;
3. Who administers it? Without available DevOps skills, the Cloud premium is almost always lower than the cost of administration time;
4. Can your data leave your infrastructure? If not, the cloud plan question does not even arise: self-hosted;
5. Is your volume predictable? Irregular or fast-growing → Cloud (elasticity works in your favor); massive and stable → self-hosting is probably more rational.

And in every case: validate the current quotas and amounts on n8n.io/pricing before committing.

Making every execution pay off from month one

Whichever plan you pick, the real economic lever is not the pricing grid: it is the time your workflows save once they are running. Rather than burning your first weeks of subscription building from an empty canvas, our catalog of ready-to-use n8n workflows provides pipelines already tested — AI agents, RAG, CRM and e-commerce automations — to import and adapt with a few settings, so that every execution deducted from your quota produces value from day one.