EN
Ihor NikolenkoGlad you're reading this. Ihor Nikolenko here, author of this blog and a member of n8n's official Creators program. Almost every conversation I have about automation with a business owner starts the same way: "Someone manually copies website leads into a spreadsheet, then someone messages the client, then someone forgets." And that's not a people problem. It's the absence of a system that handles the routine work instead of people.
Here's why this matters now, not "someday when there's time": automation tools have never been this accessible, and language models have made possible what used to take a developer a month. The difference between a business where the owner puts out fires every day and one where processes run themselves now comes down to whether you know how to build your first working workflow.
In this article, I'll explain what n8n is, in plain language and without the marketing spin: how it's built, what it does out of the box, how it differs from Make and Zapier, what it costs, and why I recommend a self-hosted server over the cloud. This is the foundation — everything else I write in the automation section builds on it.
n8n in One Minute
n8n (pronounced "n-eight-n," short for "nodemation" — nodes plus automation) is a business process automation orchestrator. If you're looking for an analogy, it's the Photoshop of the integration world: a professional tool that lets you do almost anything, without artificial limits imposed "because of your plan." It was created by Jan Oberhauser, the project is open source and lives on GitHub — when I started learning it, the repository had tens of thousands of stars; today it has several times that, making it one of the most popular projects in its category.
n8n is a professional orchestrator for business process automation and AI integrations, whether inside your own infrastructure or through a language model's API. In other words, professional software with no technical limits placed on your automations.
Technically, the system is written in Node.js and works with data in JSON format. You build a workflow out of nodes: one node receives an event, the next checks something, a third writes to your CRM, a fourth sends a message. Data flows between nodes, and you can see it at every step — that's the main reason n8n stays understandable even without programming experience. And if a standard node isn't enough, you write a few lines of JavaScript or Python right inside the workflow — or, if you're really motivated, build a custom node for your own service.
What It Does Out of the Box
- Hundreds of ready-made integrations. CRMs, messengers, spreadsheets, databases, payment systems, ad accounts — most popular services have an official node, and the community has added even more of its own.
- An HTTP Request node for everything else. If there's no official node but the service has an API, you can connect it in a few minutes. That removes the "supported / not supported" wall that plagues simpler builders.
- Every kind of trigger. Webhooks from external services, schedules, new spreadsheet rows, bot messages, incoming emails — a workflow starts from an event, not from you clicking a button.
- Code exactly where you need it. The Code node, with JavaScript and Python, lets you transform data however you like without ever leaving the workflow.
- Built-in data tables. You can now keep simple reference lists and intermediate data inside n8n itself — no need for Google Sheets, Airtable, or a separate database for every little thing.
- AI nodes. Agents, conversation memory, vector stores, calling models via API — these are all standard building blocks for assembling a chatbot or a document-processing assistant.
- Sub-workflows, error handling, versioning. The features that separate a toy from a system: one workflow calls another, and an error doesn't just vanish — it routes to a dedicated workflow with a notification.
n8n vs. Make and Zapier: Photoshop vs. Paint
I'm not against Make or Zapier as products — I'm against a business owner spending time on them that they'll later have to spend again migrating away. Here's the difference, without the emotion.
Make and Zapier are SaaS builders. You pay by the number of operations or tasks, your data passes through their servers, and your options are limited to whatever the vendor decided to add. While you only have a handful of workflows, that's convenient. Once you have dozens of automations handling a real flow of customers, the bill grows right along with the volume, and anything "nonstandard" becomes either impossible or expensive.
n8n is software you can install on your own server. The number of executions is limited only by your server's resources, your data never leaves your own infrastructure, and any logic can be extended with code. There's also a cloud version of n8n, for anyone who doesn't want to touch a server at all — but even there, you pay for workflows and executions, not for every single operation inside them.
| Criterion | Make, Zapier | n8n Cloud | Self-hosted n8n |
|---|---|---|---|
| Pricing model | By operations or tasks | By plan and executions | By server; executions aren't counted |
| Where your data travels | Through the vendor's servers | Through n8n's servers | Within your own infrastructure |
| Custom code in a workflow | Limited | JavaScript and Python | JavaScript, Python, custom nodes |
| Integrations with no official node | Depends on the vendor | Via HTTP Request | Via HTTP Request and custom nodes |
| Administration | None | None | Minimal on a managed platform, full on a VPS |
| Best for | A handful of simple workflows | A team with no technical person | A business building a system for the long run |
What It Costs, and Why I Favor a Self-Hosted Server
When I was putting together a way for readers to cut recurring costs, I ran the numbers and was surprised how much it added up to. At the time I calculated this, n8n's entry-level cloud plan cost around thirty euros a month with tax. For a business where automations are already generating revenue, that's a fair price. For someone still building out their system with no steady income yet, it's an expensive indulgence that delays getting started.
I don't seriously consider the "run it locally on my own computer" option. Sure, it's free, but without a public address, no webhook from Telegram, a payment provider, or a website form will ever reach you — you'd only be able to use the system within your own machine. And even if you work around that with tunneling tools, the computer still has to stay on all the time. The hassle outweighs the savings.
The solution I settled on is a platform that deploys n8n from a ready-made template onto your own server for around five dollars a month, complete with load monitoring, alerts, and the ability to scale the server vertically and horizontally. Yes, it takes about an hour, following a guide. But once it's done, you have a full-fledged system of your own, not a rental of someone else's. The step-by-step guide is its own article — the natural next step after this one.
Who Needs n8n, and Where to Start
Short answer: anyone with at least one process they repeat manually every day. But it delivers the most value for three types of people.
- A small business owner or independent expert. Website lead → validation → CRM → a message to the client's messenger → a reminder to the manager. One workflow that permanently kills "we forgot to call back."
- A marketer. Pulling leads from every source into one place, tagging traffic sources, automatic reports in Telegram, follow-ups for people who didn't buy.
- A startup. A first MVP with no backend: a form, a database, a payment, access — all of it can be assembled from nodes to validate an idea before hiring developers.
The First Skill: Reading JSON
The most important skill for working with n8n isn't programming — it's being able to read JSON. All data moves between nodes in this format, and once you can see that a field called email sits inside a contact object, you can plug it in anywhere you need. That's an hour or two of learning that makes you self-sufficient for most workflows.
Your First Workflow: Already Built
I don't recommend starting from a blank canvas. Grab a ready-made system that's already running on real channels: the n8n Telegram Traffic Processor checks channel subscriptions and hands out materials, coupons, and access in return, runs diagnostics, and books consultations. Import it into your own n8n, take it apart node by node, and you'll understand the system faster than any course could teach you. Then customize it to fit your needs.
And if you'd rather first figure out exactly which processes in your business to automate first, instead of building workflows just for the sake of it, a 60-minute consultation will break your business down into processes and give you a 30-day plan.
The Short Version
- n8n is an open-source automation orchestrator built on Node.js: workflows made of nodes, data in JSON, code exactly where you need it.
- Out of the box: hundreds of integrations, an HTTP Request node for everything else, triggers, built-in data tables, and building blocks for AI agents.
- Make and Zapier charge by operation and keep your data on their servers; self-hosted n8n doesn't count executions and keeps your data on your own infrastructure.
- n8n Cloud costs tens of euros a month — expensive for getting started; a local computer can't receive webhooks.
- The sweet spot for an entrepreneur is a self-hosted server on a template-based platform for around five dollars a month.
- The first skill to learn is reading JSON; the first workflow to build is one you already have — take it apart node by node.
Frequently Asked Questions
Do I need to know how to program to work with n8n?
No. Most workflows are assembled from ready-made nodes with a mouse. Programming only comes into play for nonstandard data transformations — and even then, it's a few lines in a Code node, which a language model can write for you today. What you really need is an understanding of JSON structure.
Is n8n free?
The code is open, and you can run it on your own server without paying a license fee for internal business use — n8n is distributed under what's called a "fair-code" license, and it's worth reading the terms on the official site. You only pay for the server. The developers' cloud version is a paid plan.
Why is n8n better than Make if Make is simpler?
Simpler to start with, yes. But Make charges for every operation and keeps your data on its own servers, and building nonstandard logic in it is difficult or impossible. Self-hosted n8n doesn't limit executions, lets you extend anything with code, and doesn't lock you into a vendor. If you're building a system meant to last for years rather than a workflow meant to last a month, that difference becomes decisive.
Can I connect ChatGPT or another model to n8n?
Yes, and it's one of the most common use cases today. n8n has nodes for working with language models via API, agents with memory, and vector stores for handling documents. A typical example is a bot that answers customer questions based on your knowledge base and escalates complex cases to a human.
Which workflow should I start with if I have a lot of processes?
Start with the one that steals your own time every single day and has a clear input and output: a lead comes in, it lands in your CRM, and the client gets a message. It's simple, the result is visible right away, and building it teaches you webhooks, JSON, and messaging — the three building blocks most other automations are made of.
