What is n8n, exactly?
n8n is a workflow automation tool. You build a "workflow" — a chain of steps that runs by itself. A trigger starts it (a new form entry, an email, a scheduled time), and then each step does one thing: copy a contact into your CRM, post a Slack message, add a row to a spreadsheet, send a confirmation email. You arrange these steps on a visual canvas, dragging boxes called nodes and connecting them with lines. No constant copy-paste between apps.
If you've heard of Zapier or Make, n8n does the same core job. It sits between your tools and shuttles data around so you don't have to. The name is pronounced "n-eight-n," short for "nodemation."
The one trait that sets it apart: n8n can be self-hosted. That means you can run it on a server you control instead of only on the company's cloud. Most hosted automation tools charge by the task or operation, so your bill grows every time a workflow runs. With self-hosted n8n, you pay for the server and run as many tasks as that server can handle. We use it this way in our own studio — our client and event intake forms feed self-hosted n8n workflows that route the data where it needs to go.
How does n8n actually work?
Every workflow has three parts: a trigger, some steps, and connections.
The trigger is the starting gun. Common ones are a webhook (another app pings n8n when something happens), a schedule (run every morning at 8), or a watcher on an app (a new row in Google Sheets, a new Stripe payment).
The steps are nodes. n8n ships with hundreds of pre-built nodes for popular apps — Gmail, Slack, Sheets, Airtable, Stripe, HubSpot, and many more. Each node does one action, like "send email" or "create record." You drop them on the canvas and draw a line from one to the next so data flows down the chain.
Between nodes you can shape the data: filter it, split it, merge two sources, or add an if/then branch so the workflow takes different paths. When the built-in nodes don't cover something, n8n lets you write a little JavaScript or Python, or call any service that has an API. That flexibility is a real edge over simpler tools that lock you into fixed actions. You build and test in the editor with sample data, then switch the workflow on.
Why does the pricing model matter?
This is the heart of why small businesses look at n8n.
Most automation tools meter usage. Zapier counts "tasks"; Make counts "operations." Every step a workflow runs nibbles at your monthly quota, and a busy automation can burn through it fast. Roughly, plans start around $20–30/mo for Zapier and $10–16/mo for Make (approximate, as of 2026 — verify current pricing). The catch is direction: as your automation grows, that number climbs.
Self-hosted n8n flips the model. You rent a small server — a VPS for roughly $5–20/mo as of 2026 — and run your workflows on it. No per-task fee sits on top. Whether a workflow runs 100 times or 100,000 times, the server cost stays flat (until you genuinely outgrow the machine and size up).
This doesn't make n8n automatically cheaper. For a handful of light automations, a hosted plan can cost about the same and save you the upkeep. The flat model pays off once you run a lot of steps, or many workflows, and a metered bill would otherwise keep growing. Prefer not to manage a server? n8n Cloud starts around $20/mo (approximate, as of 2026 — verify).
What is the fair-code license?
n8n is "fair-code," not classic open source, and the difference is worth understanding before you commit.
In practice, fair-code means the source code is public and you can run n8n yourself for free, view it, change it, and self-host it for your own business. For the vast majority of small businesses, that's all you'll ever touch — you get the full tool at no license cost.
The limits only kick in at the edges. The license restricts reselling n8n as a hosted product or building a competing paid service on top of it. Unless you're planning to launch "n8n-but-it's-mine" as a commercial offering, those restrictions won't affect you.
Why does this matter? Two reasons. First, you own your setup. The workflows you build live on your server, and you keep them even if you stop paying anyone. Second, there's no vendor lock-in on the data — your information isn't trapped inside someone else's cloud. For a business that wants control and predictable cost, fair-code lands in a comfortable middle: more freedom than a closed SaaS tool, with a few guardrails that, honestly, you'll likely never bump into.
What's the honest trade-off?
Self-hosting is the catch, and we won't pretend it's free of effort.
When you run n8n on your own server, you're responsible for it. That means keeping the software updated, taking backups so a crash doesn't erase your workflows, and making sure the server stays online and reasonably secure. None of this is hard for someone technical, but it is ongoing. A workflow that quietly stops at 2 a.m. is your problem to notice and fix.
The hosted tools you'd compare against — Zapier, Make, or n8n's own cloud — handle all of that for you. You trade money for not having to think about servers. That's a fair deal for plenty of businesses, and we'll say so when it fits you better.
So here's the honest read. If you have light, occasional automation and no one in-house who likes servers, a hosted tool is probably simpler and the cost difference is small. If you run a growing pile of automations, want flat and predictable cost, or care about owning your data, self-hosted n8n earns its keep — as long as someone keeps an eye on the upkeep, whether that's you or a partner who maintains it for you.
Is n8n the right fit for your business?
Start with a plain question: are you doing the same digital chore over and over by hand? Copying form entries into a spreadsheet, sending the same follow-up email, moving data between two apps that don't talk. If yes, automation will help, and n8n is a strong candidate.
n8n is a good fit when you run several automations or high-volume ones, want custom logic or a bit of code, care about keeping data on your own server, or simply don't want a bill that climbs with every task. It's also a fine pick if you want a tool you fully own.
It may be overkill if you have one or two simple automations and nobody to handle server upkeep. In that case, a hosted tool is the honest recommendation — sometimes the right answer is that you don't need to self-host anything.
If you'd rather have it built and maintained for you, that's what we do. See our n8n workflow development service, or weigh the three tools side by side in our n8n vs Make vs Zapier comparison. Either way, the goal is the simplest setup that takes the busywork off your plate.