What is n8n and how does it work? n8n is an open-source workflow automation tool that lets you connect apps, APIs, and services using a visual node-based editor. You build workflows by chaining together "nodes" — each one does a single job. It runs self-hosted or in the cloud, costs nothing to start, and handles logic that Zapier simply can't.
Somewhere between "I'll just do this manually" and "we need to hire a developer," there's a tool called n8n. It sits in that sweet spot where a reasonably technical person — or an unusually patient non-technical one — can automate genuinely complex workflows without writing a full application. It's been quietly gaining a cult following among developers, ops teams, and solo builders who've either outgrown Zapier or never wanted to pay Zapier's prices in the first place. If you've heard the name but never quite understood what it does or why people get excited about it, this is the article you were looking for.
What n8n actually is (no jargon, no nonsense)
n8n (pronounced "n-eight-n," though you'll hear "en-eight-en" everywhere) is a workflow automation platform. The name is shorthand for "nodemation" — n, then 8 letters, then n. Same trick as i18n for internationalisation. Nerdy, slightly annoying to spell, completely on brand.
At its core, n8n solves a very old problem: you have data in one place, and you need it to do something in another place. A form submission should create a task in your project management tool. A new customer in your CRM should trigger a welcome email sequence. A daily report should be pulled from a database and dropped into a Slack channel at 9am.
You could write code for all of this. Or you could use n8n and build it visually in a fraction of the time.
It's open-source, licensed under a "fair-code" model — which means you can self-host it for free, modify it, inspect every line of it, but you can't sell it as a hosted service without a commercial agreement. For the vast majority of users, it's effectively free.
Jan Oberhauser created it in 2019. It now has hundreds of built-in integrations, an active community, and enterprise customers running it at serious scale. Not bad for something that started as a side project.
How n8n works: nodes, workflows, and triggers explained
The basic unit in n8n is the node. Each node does exactly one job. Fetch data. Transform it. Send it somewhere. Make a decision. That's it.
You connect nodes together in a workflow. Data flows from left to right, node to node, like water through pipes (except when things break, it's less relaxing than water). Each node receives the output from the previous one, does its thing, and passes the result forward.
A workflow starts with a trigger node. Triggers are how n8n knows when to run. There are three main types:
- Webhook triggers — an external service sends data to a URL n8n gives you, and the workflow fires immediately.
- Schedule triggers — the workflow runs at a set time. Every morning at 8am. Every hour. Every Monday.
- App-specific triggers — some integrations can watch for events directly, like a new row in a Google Sheet or a new issue on GitHub.
After the trigger, you add action nodes. There are hundreds of built-in ones: Slack, Gmail, PostgreSQL, HTTP Request, Notion, Airtable, Stripe, Shopify — the list keeps growing. Each node has a settings panel where you configure it and map data from previous nodes using n8n's expression syntax.
The Function node is where n8n separates itself from simpler tools. Inside it, you write JavaScript. Real JavaScript. You can transform data, run logic, call external libraries, handle errors, loop through arrays — whatever you need. It's a trapdoor in the floor of the no-code interface, and it's wonderful.
There are also IF nodes for branching, Merge nodes for combining data streams, and Loop nodes for iterating. You can build genuinely complex logic without it turning into spaghetti. (Though it can turn into spaghetti. That part's on you.)
What is n8n and how does it work compared to the competition?
The usual comparison is Zapier. Fair enough. Both connect apps and automate workflows. But they're aimed at different people.
Zapier is polished, beginner-friendly, and lives entirely in the cloud. Its pricing scales with usage in a way that can sting once you're running serious volume — thousands of "tasks" per month adds up fast. It's excellent for simple two-step automations where you don't need much control.
n8n gives you control. You can run it on your own server, own your data, write custom logic, and handle complex multi-step workflows with branching and loops. The interface takes longer to learn. The payoff is considerably bigger.
Make (formerly Integromat) sits between them — more visual complexity than Zapier, cloud-hosted, good for moderately complex workflows. n8n beats it on flexibility and cost at scale.
Rule of thumb: if you're a non-technical person who just needs Gmail to talk to Trello, use Zapier. If you're a developer or technical ops person who wants real power without a per-task pricing model hanging over you, n8n is your thing.
Self-hosted vs cloud: which one should you actually pick?
n8n gives you two ways to run it.
Self-hosted means you spin it up on your own server. Docker makes this genuinely easy — there's an official image, the docs are solid, and you can have it running in under an hour. You bring your own database (PostgreSQL is recommended for anything serious), configure your credentials, and you're off. The cost is whatever your server costs. A small Digital Ocean or Hetzner instance handles a lot of workflows for a few dollars a month.
n8n Cloud is the managed option. You don't touch a server. Updates happen automatically. Support is included. You pay a monthly subscription. It's worth it if infrastructure management is genuinely not your thing, or if you're running this for a business that needs uptime guarantees without a sysadmin on call.
For individuals and small teams comfortable with Docker: self-host. For companies who want someone else to handle it: cloud. The functionality is the same either way.
The thing most n8n explainers quietly skip over
Most articles about n8n focus on the shiny stuff — the integrations, the visual editor, the fact that it's free. What they don't mention is error handling, and it matters a lot in production.
n8n workflows fail. An API times out. A webhook sends malformed data. A database connection drops. When this happens to a Zapier automation, Zapier catches the error, logs it, and emails you. When it happens in a badly configured n8n workflow, it can just... silently stop.
n8n does have error workflows — a special workflow that triggers when another workflow fails. You can configure it to send yourself a Slack message, log the error to a database, or retry the failed execution. But you have to set this up deliberately. Nine times out of ten, the beginner n8n setup has no error handling at all.
If you're running n8n for anything that matters, configure an error workflow. Use a persistent database (not SQLite in production). Set up execution logging. This isn't glamorous advice, but it's the difference between n8n being a toy and n8n being a reliable part of your infrastructure.
Also worth knowing: n8n's community forum is genuinely one of the better ones out there. When you get stuck — and you will get stuck — it's a decent place to find answers without feeling like you've wandered into a Reddit argument.
My honest take: who should use n8n and who shouldn't bother
Here's my strong opinion: n8n is one of the best tools available for developers and technical ops people who need automation with real flexibility. Full stop. The combination of visual editing, custom JavaScript, self-hosting, and a generous free tier makes it genuinely hard to beat for the right use case.
But "the right use case" is doing a lot of work in that sentence.
n8n is not beginner-friendly in the way Zapier is. The interface is more complex. The concepts — nodes, expressions, execution modes — have a learning curve. If someone has never thought about APIs, webhooks, or data transformation before, they will find n8n frustrating. Zapier will serve them better, even at the higher price.
n8n is also not a good fit if you need enterprise-grade support out of the box without budget or technical resource to manage self-hosting. The cloud plan addresses this, but it's a paid product with pricing that scales with usage.
Here's when I'd tell someone not to bother with n8n: if your automations are simple (trigger A does action B, no logic required), if you have no one on the team who can troubleshoot a Docker container, and if you're moving fast and need something running in 10 minutes. Use Zapier. Pay the tax. Move on.
But if you've hit Zapier's limits — either the logic limits or the pricing limits — and you want something that can grow with you, n8n is where you end up. Most people who find it don't go back.
The short version
n8n is a workflow automation tool built on a node-based visual editor. Trigger something, transform the data, do something with it. It's open-source, self-hostable, and free to run on your own server. The Function node lets you drop into JavaScript when drag-and-drop isn't enough. It's more powerful than Zapier, less forgiving than Zapier, and considerably cheaper than Zapier once you're running real volume. Set up error handling. Use a proper database. And try not to spend three hours automating something that would have taken twenty minutes by hand — we've all been there, and we'd do it again.