Pricing

How much does an n8n automation program cost?

The short answer

An n8n automation program of 5 to 15 connected workflows typically costs $15,000 to $50,000 and takes four to ten weeks. A single-department program on n8n Cloud sits at the low end, while a cross-functional program on self-hosted n8n with a Zapier or Make migration, shared error handling and monitoring sits at the high end. Ongoing costs are n8n hosting or an n8n Cloud plan, model usage for AI steps, and someone to own updates.

TierPriceWhat is included
Starter program$15,000–$25,000Five to seven workflows for one department, n8n Cloud or a simple self-hosted setup, a shared error-alert workflow, and documentation for each workflow. Four to six weeks.
Department program$25,000–$38,000Eight to twelve workflows with several AI steps, self-hosted n8n with Postgres and backups, a reusable sub-workflow library, run logging, and two training sessions for your owner.
Cross-functional program$38,000–$50,000Twelve to fifteen workflows across finance, sales and operations, migration from Zapier or Make with a parallel run, queue mode for volume, monitoring and a full runbook. Up to ten weeks.

What drives the cost

Number of workflows
The obvious driver, though not linear. Workflows that share apps and data reuse credentials, sub-workflows and mappings, so the tenth workflow costs less than the first.
Hosting choice
n8n Cloud needs almost no setup. Self-hosting adds a server, a Postgres database, backups, SSL, and queue mode with workers if volume is high.
Migration from Zapier or Make
Rebuilding existing Zaps or scenarios needs an inventory, a parallel run and a cutover plan. It is cheaper than designing from scratch but not free.
Restricted or unusual APIs
Apps without an n8n node are reached through the HTTP Request node. Systems like ADP, Yardi or ServiceTitan usually need partner or customer-specific API approval, which can add weeks.
AI steps across the program
Classification, extraction and drafting steps each need test data and a fallback. A shared AI sub-workflow with one prompt library keeps this manageable.
Shared foundations
A central error workflow, naming conventions, credential management and run logging are built once and make every later workflow cheaper to maintain.
Handover and training
If your team will own n8n afterward, budget for documentation and hands-on sessions. If we maintain it, less training is needed.

The short answer

A program of 5 to 15 n8n workflows costs $15,000 to $50,000 with Lumeor and takes four to ten weeks. Most small and mid-sized companies land in the middle: eight to twelve workflows for one or two departments, self-hosted, with a few AI steps.

A program is not just several workflows billed together. It includes the shared plumbing that makes many workflows maintainable: one error handler, one logging approach, one set of credentials, and sub-workflows that several automations call. For a one-off workflow, see what a single workflow automation costs.

Where the money goes

PhaseShare of effortWhat happens
Inventory and prioritization10–15%List candidate processes, score them by hours saved and risk, pick the set
Foundations10–20%Hosting, credentials, error workflow, logging, naming and folder conventions
Workflow builds40–50%Triggers, mappings, AI steps, approvals for each workflow
Testing and parallel runs10–15%Run each workflow against real data, compare with the manual or old automated result
Handover10–15%Runbook, per-workflow docs, training, ownership plan

Foundations look like overhead on the first workflow and pay off by the fifth. Without them, each workflow handles failures its own way, and nobody can tell at a glance what broke overnight.

What it costs to run n8n

  • Hosting. n8n Cloud is billed by plan, with limits on monthly executions. Self-hosted n8n is billed by your cloud provider for the server, database storage and backups. Queue mode adds a Redis instance and worker processes. Check n8n’s current plans before choosing.
  • Model usage. AI nodes call OpenAI, Anthropic or another provider and are billed per token. Cost scales with how many items pass through AI steps and how long the text is. Sending simple classification to a small model such as Claude Haiku 5.5 keeps this predictable.
  • App API access. Some apps only expose their API on higher plans. Across 10 or more workflows you may hit this once or twice.
  • Monitoring and upkeep. Uptime checks, log retention and n8n version updates. On self-hosted setups someone needs to apply updates on a schedule.

The trade-offs between the two hosting models are laid out in n8n Cloud vs self-hosted n8n.

How to keep the cost down

  • Cut the list. Most inventories include automations that save a few minutes a month. Leave them out.
  • Group by system. Workflows that touch the same apps share credentials and mappings, so building them together is cheaper.
  • Start on n8n Cloud. You can move to self-hosted later if volume or data rules require it.
  • Name an internal owner early. A person who joins testing needs less formal training at the end.

When a program is the wrong buy

If you have only two or three processes worth automating, buy them as individual workflows. If your company runs almost entirely on Microsoft 365 and your IT team already supports Power Automate, that may fit better than adding n8n. If nobody in-house will ever touch the workflows and volume is modest, Zapier’s simplicity can be worth its per-task pricing. Our Zapier to n8n migration guide covers when switching is worth the effort.

How Lumeor prices an n8n program

We start with an inventory session, then quote a fixed price for a named list of workflows, the hosting setup and the handover. Adding workflows is quoted separately. For an example of this kind of work, see our n8n automations suite case study.

Frequently asked questions

Is self-hosted n8n really cheaper than n8n Cloud?

It removes the per-execution plan limits, and the Community Edition has no license fee for internal business use. You still pay for a server, a database, backups and someone to apply updates and watch uptime. At low volume n8n Cloud is often simpler and cheaper overall. At high volume, or when data must stay in your own cloud, self-hosting usually wins.

Why not just build the workflows one at a time?

You can, and for two or three workflows that is the right call. Past five, a program is cheaper because credentials, error handling, logging and common sub-workflows are built once. It also gives you one consistent system instead of a pile of one-off automations built in different styles.

Can you move our Zapier or Make automations to n8n?

Yes. We inventory what exists, drop automations nobody uses, rebuild the rest in n8n, run both in parallel for a short period, then switch over. Expect most of the savings to come from no longer paying per task on high-volume workflows.

Who maintains the workflows after launch?

Either your team or ours. Every program ends with documentation and a walkthrough. If you do not have a technical owner, an optional monthly support plan can cover fixes, app changes and small additions.

Do we need an engineer on staff to run n8n?

Not for n8n Cloud. A technically comfortable operations person can own day-to-day changes. Self-hosted n8n needs someone who can manage a server and database updates, or a support arrangement that covers it.

Next steps