Complete guide · 2026
n8n for business: is it right for you?
Should your business use n8n? What it's used for, the real yearly cost, Cloud vs self-hosted, security, AI agents, and who maintains it after the build.
Abhijeet Singh · AI automation and Zoho CRM consultant
Updated 6 Nov 202614 min read Top Rated on Upwork

The short answer
Four ways to run your automation
Three of them are n8n, run by different people. Decide who will own it before you decide where it runs.

OPTION 01
n8n Cloud
Choose it when you have a small team, no IT staff and moderate volume, and want to start this week.
- Runs
- n8n's servers in the EU
- Cost
- From €20 a month, billed annually

OPTION 02
Self-hosted n8n
Choose it when you have in-house IT, strict data rules or high volume, and someone who will patch it every two weeks.
- Runs
- Your own server
- Cost
- Community Edition free; you pay for the server and the upkeep

OPTION 03
Managed n8n
Choose it when you want n8n's flexibility without hiring for it, with everything in your own accounts.
- Runs
- Your Cloud workspace or your server
- Cost
- n8n plan or server, plus a monthly support plan

OPTION 04
Not n8n
Choose it when you need a few simple, low-volume automations and nobody to look after them.
- Runs
- Zapier, Make or your CRM
- Cost
- Per task or per credit
On this page 13 sections
n8n is a good fit for a business that has repeatable work moving between several tools and someone who will own the workflows once they are built. It is the wrong fit if you need a handful of simple automations and nobody to look after them. In that case Zapier, Make or your CRM's own automation will cost you less time.
The software is the cheap part. n8n Cloud starts at €20 a month, and the self-hosted Community Edition is free. What decides whether n8n works for you is who builds it, who patches it and who fixes it when an outside app changes. This guide covers what businesses use n8n for, what it costs over a year, Cloud versus self-hosted, security, AI agents, and how to hand it over without depending on one person.
Which option should you use?
There are four realistic ways to go. Three of them are n8n, run by different people. The fourth is not using n8n at all.
n8n Cloud | Self-hosted n8n | Managed n8n | Not n8n | |
|---|---|---|---|---|
| What it is | n8n's own hosted service | The free Community Edition (or paid Business plan) on your own server | n8n built and looked after for you, in your accounts | Zapier, Make, or the automation built into your CRM |
| Who runs the server | n8n | You | Your consultant | The vendor |
| Who applies security updates | n8n, automatically | You, every time one ships | Your consultant, on an agreed schedule | The vendor |
| Software cost | €20 a month (Starter) or €50 a month (Pro), billed annually | Community Edition free; you pay for the server | n8n plan or server, plus a monthly support fee | Per task or per credit, rising with volume |
| Best for | Small teams with no IT staff and moderate volume | Teams with in-house IT, strict data rules or high volume | Teams that want n8n without hiring for it | A few simple, low-volume automations |
| Main risk | Hitting your execution limit; slower support | An unpatched server, or lost work with no backups | Depending on one outside person if nothing is documented | Cost climbs with volume; complex logic gets awkward |
| Where your data sits | EU (Microsoft Azure), no choice of region | Wherever your server is | Your choice | The vendor's regions |
If you take one thing from this table: decide who will own n8n before you decide where it runs.
What is n8n, in plain business terms?
n8n is a workflow automation tool. Every workflow starts with a trigger, such as a form submission, a new CRM record, a WhatsApp message or a schedule. It then runs steps: look something up, reshape the data, decide which branch to take, ask an AI model, write to another system, send an alert. You build workflows on a visual canvas, and you can add code where a step needs real logic.
Three things set it apart for a business:
- You can run it on your own server. The Community Edition is free for your own internal business use under n8n's Sustainable Use License (n8n licence).
- You pay per workflow run, not per step. n8n's pricing is based on monthly executions "regardless of complexity" (n8n pricing). A 20-step workflow that runs once is one execution.
- It handles harder logic. Branches, loops, retries, separate error workflows, code steps and AI agents are built in.
It is not a niche tool any more. n8n lists 2,615 integrations and 13,820 community templates, raised money at a $2.5 billion valuation in October 2025, and took a strategic investment from SAP in May 2026, when it reported 1.7 million monthly active builders (n8n and SAP).
What do businesses actually use n8n for?
Most useful n8n work moves information between systems that don't talk to each other, so people stop copying it by hand. Grouped by team:
- Sales and leads: pull leads from website forms, Meta lead ads, marketplaces and WhatsApp into the CRM, remove duplicates, assign an owner and alert the right rep.
- Customer conversations: WhatsApp assistants that answer common questions, collect the details sales needs, and hand over to a person.
- Finance and operations: read supplier invoices from email into the accounting system, keep orders and stock in step between the CRM and the books, send payment reminders.
- Reporting: collect numbers from several tools into one sheet or dashboard every morning.
- AI inside a process: summarise a call, sort an enquiry by type, or draft a reply that a person approves before it goes out.
A CRM is where most of this lands. Zoho CRM, for example, has no ready-made n8n trigger, so the usual setup is a Zoho workflow rule that calls an n8n webhook, with n8n checking for duplicates before it writes anything back. The full setup is in how to connect Zoho CRM to n8n. If you also want AI agents working on CRM records, the guide to AI agents for Zoho CRM compares n8n with Zoho's own Zia Agents.
Two live examples from my own work: a multilingual WhatsApp sales assistant for a freight forwarder, built on n8n, qualifies enquiries in three languages, keeps every conversation in PostgreSQL and alerts sales the moment a quote is requested. For a B2B packaging manufacturer, n8n connects Zoho CRM, Books, Desk, Analytics and People into one system.
When is n8n the wrong tool?
n8n gets recommended for everything at the moment. It is the wrong choice when:
- You need three or four simple automations. "New form entry, add a row, send an email" runs fine on Zapier or your CRM's built-in rules, with nothing to host or patch.
- Nobody will own it. If no one reads the error alerts, a broken workflow can run silently for days. On Reddit's r/automation, one team described dropping n8n after three months because no one but its builder could change anything (thread).
- The whole job lives inside one system. If every step happens inside Zoho or HubSpot, that platform's own automation is easier to support.
- You need data hosted outside the EU and don't want to run a server. n8n Cloud is hosted in the EU, with no choice of region at the time of writing (n8n trust centre).
- You want your customers to build workflows inside your product. That needs n8n's commercial Embed licence, not the free edition.
A quick test: n8n is worth it when the work crosses at least two systems, runs often or needs real logic, and has a named owner. If any of the three is missing, start simpler.
n8n Cloud, self-hosted or managed: which should you choose?
n8n Cloud
n8n runs the servers and applies updates for you. As of November 2026, Starter costs €20 a month for 2,500 executions and Pro €50 a month for 10,000, both billed annually; n8n's own page lists prices in euros (n8n pricing). Starter allows 5 workflows to run at once and keeps execution logs for 7 days; Pro keeps them for 30.
The limits to plan around are the execution quota and memory. Starter instances get 640 MiB of memory, so very large files or heavy workflows can run out (n8n Cloud docs). On n8n's forum, Cloud customers have reported a looping workflow using up a whole month of executions (forum). Add an error alert and check usage weekly.
Self-hosted n8n
The Community Edition is free and has the full workflow builder. It leaves out team and governance features: single sign-on, Git version control, separate environments, external secrets, log streaming, and sharing workflows and credentials between users (n8n editions). The Business plan adds those for €667 a month, self-hosted only.
You own everything else: the server, the database, backups, SSL certificates and updates. From n8n 3.0 onwards, self-hosting is Docker only. Use PostgreSQL from day one rather than the default SQLite; the n8n forum has reports of SQLite installs running out of memory and of an upgrade that lost two weeks of workflow changes because there was no backup. More detail: self-hosting n8n in 2026.
Managed by a consultant
A consultant builds and runs n8n for you, but inside your accounts: your Cloud workspace or your server, your API credentials, your domain. You pay for the build and then a monthly support plan that covers updates, monitoring and small fixes. n8n's licence FAQ states that "consulting and automation services are explicitly permitted" (licence FAQ).
This route only works if the hand-back is real. See who owns it after it's built below.
What does n8n really cost over a year?
n8n counts one execution each time a workflow runs, however many steps it has. Zapier counts every action step as a task, and Make counts credits per step it runs (Make credits). That difference is why n8n gets cheaper as workflows get longer.
A worked example. A 15-person company runs six workflows: lead intake, CRM updates, WhatsApp follow-up, invoice capture, a daily report and an error alert. Together they run about 200 times a day, roughly 6,000 executions a month.
- n8n Cloud: Starter's 2,500 executions is too small, so Pro at €50 a month, or €600 a year. Updates are included.
- Self-hosted Community Edition: no licence fee. A practitioner who moved 12 small-business clients from Zapier to n8n reported server costs of about $20 to $40 a month (write-up), so $240 to $480 a year. Add the upkeep: n8n now publishes security updates every two weeks, so plan for about 26 updates a year. At 30 to 60 minutes each, including a backup check, that is 13 to 26 hours of someone's time.
- The same work on Zapier: if each workflow has five action steps, 200 runs a day is 1,000 tasks a day, about 30,000 a month.
From my own setup: my own n8n server runs on a small VPS that costs me about $10 a month. The server bill is rarely the hard part of self-hosting. The updates, backups and the hours to look after them are.
The build costs the same whichever way you run it, and in year one it is usually the biggest number. The line people forget is maintenance. For the full comparison with Zapier, see n8n vs Zapier.
How does n8n compare with Zapier and Make?
- Ease of use: Zapier is the easiest for non-technical staff. Make sits in the middle. n8n needs at least one person who is comfortable reading data and error messages; the learning curve is the most common complaint in n8n's Capterra reviews (Capterra).
- Pricing: per task on Zapier, per credit on Make, per workflow run on n8n.
- Hosting: only n8n lets you run it on your own server.
- Logic: n8n handles branching, loops, code and error workflows most fully.
Many businesses use two of them: Zapier or the CRM for quick, simple jobs, and n8n for the high-volume or complicated ones.
What a real Zapier-to-n8n move looked like
I moved about 20 workflows for a US manufacturing client from Zapier to n8n. Zapier was costing them about $70 a month and gave them little freedom to build what they needed. Their n8n now runs on a server that costs about $10 a month, and the same server also runs other open-source tools they use, including an AI agent platform. They also have far more control over what their workflows can do, and the workflows run more reliably.
Is n8n secure, and who patches it?
On n8n Cloud, n8n patches the platform. Its trust centre lists SOC 2 Type 2, SOC 3 and GDPR, and Cloud data is hosted in the EU on Microsoft Azure and encrypted at rest (n8n security).
On a self-hosted server, patching is your job, and it matters. In January 2026 n8n disclosed CVE-2026-21858, nicknamed "Ni8mare": a flaw rated 10 out of 10 that let attackers take over unpatched servers without logging in. It was fixed in version 1.121.0 (n8n advisory), yet Censys still counted about 26,500 exposed servers (Censys). Five more critical issues followed in February 2026, and n8n now ships security updates every two weeks.
Update on a schedule
Every two weeks, in line with n8n's security updates. Read the release notes first, because major versions such as 2.0 and 3.0 remove features.
Back up before every update
Back up the database and the encryption key. Without the key, saved credentials can't be read on a new server.
Use PostgreSQL for anything that matters
SQLite is fine for testing, not for workflows your sales depend on.
Give each workflow only the access it needs
A workflow that reads invoices does not need permission to delete CRM records.
Review AI-built workflows before switching them on
Check loops and limits. An unchecked loop can burn a month of executions or flood a customer with messages.
Can n8n run AI agents safely?
Yes, if the agent is one step in a workflow with checks around it. n8n has an AI Agent node that picks its own tools, Evaluations for testing AI output against real examples, and MCP support, so assistants like Claude can call your workflows (n8n MCP docs).
AI steps fail in a different way from normal steps: the workflow succeeds, but the answer is wrong. A safe setup:
- Put a human approval step before anything that messages a customer or changes money, prices or deal stages (human-in-the-loop AI agents).
- Check the AI's output against a fixed format before the next step uses it, and stop the run if it doesn't match.
- Test with real past examples before going live, and again after any prompt or model change (testing AI workflows with n8n Evaluations).
- Log every decision the agent makes, so you can see why it did something.
- Cap loops and tokens, so one bad input can't run up your bill.
If you want an AI assistant to use your workflows as tools, the n8n MCP server guide covers how that works.
Who owns it after it's built?
This is where most n8n projects succeed or fail. The usual regret is a set of workflows only one person understands. Before anyone starts building, agree on:
- Your accounts. The n8n workspace or server, every API credential and the domain are in your company's name, not the builder's.
- One page per workflow. What triggers it, what it changes, and what to do when it fails.
- Error alerts to a named person. Silent failures are the expensive ones (n8n error handling).
- Backups you can restore without the builder, tested at least once.
- A plan for version upgrades. n8n 3.0 has been in beta since 27 October 2026, with the stable release expected in early December 2026. The upgrade is one way, so test it on a copy first (what n8n 3.0 breaks; the n8n 2.0 upgrade).
- A written support agreement. A short warranty after go-live, then a monthly plan, with a clear line between a fix and new work.
What I hand over: when I build n8n for a client, handover includes written documentation for every workflow. After that, there's an optional monthly retainer that covers updates, fixes and whatever else the client needs.
How do you start your first n8n project?
- Pick one process that crosses at least two systems and happens every day.
- Write down how it is done by hand today, and what "done" looks like.
- Estimate how many times it runs a month, so you can pick a plan.
- Name the owner.
- Build it and test the failures as well as the happy path: duplicate leads, an app that times out, a CRM record written halfway.
- Run it next to the manual process for a week or two before you switch the manual one off.
If you hire someone, ask these before you sign:
- Will everything be built in my accounts?
- How do you test what happens when an app fails or sends bad data?
- What documentation do I get at handover?
- What happens when an app we connect to changes its API?
- Can someone on my team maintain this without you?
A good answer to the last question is the best sign you will get. If you want n8n built and looked after for you, that is what I do: n8n automation for businesses.
Key takeaways
- n8n fits when the work crosses several systems, runs often or needs real logic, and has a named owner.
- The licence is the smallest cost. Hosting, updates and maintenance hours are the real budget.
- n8n Cloud means n8n patches it; self-hosting means you patch it, every two weeks.
- Treat AI steps as fallible: approval before anything customer-facing, a fixed output format, and tests.
- Get everything in your own accounts, documented, with backups you can restore yourself.
Common questions
Is n8n free?
The Community Edition is free to self-host for your own business. n8n Cloud starts at €20 a month on the Starter plan, billed annually.
Can I use n8n for commercial work?
Yes, for your own internal business processes, and consultants may build workflows for clients. You need a commercial licence to host n8n for customers to build their own workflows, or to white-label it.
Do I need to be technical to use n8n?
Not for simple workflows. To own workflows your business depends on, you need at least one person who is comfortable reading data and error messages, or a consultant on a support plan.
Where does n8n Cloud store my data?
In the European Union, on Microsoft Azure. At the time of writing there is no choice of region.
Is n8n 3.0 out?
It has been in beta since 27 October 2026, and n8n expects the stable release in early December 2026. The upgrade is one way, so test it on a copy first.
Does n8n replace my CRM?
No. n8n moves data between your CRM and your other tools. The CRM stays the record of your customers and deals.
In this topic
Every article in this guide
Step-by-step posts that go deeper on one part of n8n for business.
- n8n Handover Checklist: What Clients Should Get in 2026Use this n8n handover checklist to get the docs, backups, credentials, error alerts and update plan you need before signing off an automation build.12 Nov 2026
- n8n License Explained: What Businesses and Agencies Can DoThe n8n license explained in plain English: what businesses and agencies can do for free, and when hosting, embedding or white-labelling needs a paid deal.10 Nov 2026
- n8n Cost Per Year in 2026: A Real Worked Examplen8n cost per year, worked out: Cloud vs self-hosted for 20 workflows, with server, build, maintenance and upgrade costs so you can budget with real numbers.9 Nov 2026
- Google Workspace Studio vs n8n in 2026: What to Build WhereGoogle Workspace Studio vs n8n in 2026: what each tool actually owns, the limits that decide it, and a clear rule for which automations belong where.5 Nov 2026
- n8n Access Control in 2026: Projects, Roles and Limitsn8n access control explained: instance roles versus project roles, where projects stop isolating data, and the credential leak most teams miss.5 Nov 2026
- n8n Security Updates in 2026: A Self-Hoster's Patch Playbookn8n security updates now land every two weeks. A practical patching playbook for self-hosted instances: release lines, triage, upgrades and hardening.5 Nov 2026
- n8n Staging to Production: The 2026 Promotion PlaybookMove n8n staging to production safely: Git environments, .n8np packages, what travels, credential gotchas and a rollback plan that actually holds.5 Nov 2026
- n8n vs Activepieces in 2026: A Practical Decision Guiden8n vs Activepieces in 2026: how licensing, billing units, self-hosting and extension models really differ, and the criteria that decide your pick.5 Nov 2026
- n8n vs Make in 2026: Pricing, Limits and Trade-Offsn8n vs Make in 2026: how execution billing beats per-module credits, where each platform wins, and the n8n 3.0 migration to plan for before you commit.5 Nov 2026
- n8n 3.0 Breaking Changes: What to Fix Before You Upgraden8n 3.0 is in beta, with stable due in early December 2026. See what breaks, how to run the migration report, and a four-week plan to upgrade safely.4 Nov 2026
- n8n Evaluations in 2026: Test AI Workflows Before They Breakn8n evaluations catch AI quality drift before your customers do. Which metrics to use, what each plan tier unlocks, and how to build a regression suite.27 Aug 2026
- n8n Error Handling in 2026: Stop Silent Workflow Failuresn8n error handling in 2026: how to layer node retries, error workflows, Stop and Error checks, and monitoring so workflows never fail silently.15 Aug 2026
- The n8n 2.0 Upgrade in 2026: What Breaks and What to FixThe n8n 2.0 upgrade changed defaults, not features. Here is what breaks in 2026, which environment variables to test first, and a migration order that works.14 Aug 2026
- Self-Hosting n8n in 2026: A Founder's Decision GuideSelf-hosting n8n in 2026 can cut costs and keep data in-house, but only when it fits your team. A practical framework for self-host versus cloud.26 Jul 2026
- n8n MCP Server: Turn Workflows Into AI Agent Tools (2026)n8n MCP server explained: expose workflows as AI agent tools using the July 2026 MCP spec update, with setup steps, examples, and security tradeoffs.6 Jul 2026
- n8n vs Zapier for Startups: Which Automation Platform Should You Choose in 2026?A practical founder-focused comparison of n8n and Zapier, covering ease of use, flexibility, costs, AI workflows, and which platform startups should choose in 2026.29 May 2026
Want n8n built and looked after?
I build n8n automations for service businesses in the US, UK, Australia and the UAE, inside your own accounts, documented, with error alerts and a support plan. Tell me the process; I'll tell you whether n8n is the right tool.
Related resources
Go deeper
Related posts, the service page and real builds connected to this guide.
Further reading
Article
Read: How to Connect Zoho CRM to n8n: Setup, Webhooks and Duplicates
Connect Zoho CRM to n8n the reliable way: the right data centre, OAuth setup, webhooks for new records, duplicate checks, and the updates that wipe data.
Article
Read: Human-in-the-Loop AI Agents: The 2026 Approval Framework
Human-in-the-loop AI agents don't need approval on every action. Here's the four-tier risk framework that keeps AI agent oversight tight in 2026.
Proof pages
Case study
See case study: Multilingual WhatsApp Sales Bot for an International Freight Forwarder
A WhatsApp AI sales assistant that qualifies freight enquiries in three languages, remembers every conversation, and alerts the sales team the moment a quote is requested.
Case study
See case study: Complete Zoho Stack for a B2B Packaging Manufacturer
One Zoho operating system for a B2B packaging manufacturer — sales, service, inventory, accounting, ticketing, and analytics — replacing the legacy Excel and Salesforce files the business used to run on.
n8n Cloud
Self-hosted n8n
Managed n8n
Not n8n