If you run a small business, the right question isn\u2019t \u00abHow much can I automate?\u00bb but \u00abWhat two or three things, right now, are wasting my time every week?\u00bb n8n is one of the tools that lets you eliminate those things without necessarily having to hire a developer. In this article, I\u2019ll explain what it is, how it works, and when you really need it\u2014without promising you\u2019ll \u00absave 90% of your time,\u00bb because that\u2019s not how it works.<\/p>\n\n
n8n is a platform for building automations<\/strong> connecting the tools you already use: the website, email, CRM, management software, spreadsheets, WhatsApp, and hundreds of other services. You do it visually, dragging and dropping blocks and connecting them with arrows: each block does one thing, the arrow says \u00abthen do this.\u00bb.<\/p>\n Two features make it interesting for business owners. The first: it is Fair-code and self-hostable<\/strong>, This means you can install it on your own server and use all its features without a per-user fee. Second, it has hundreds of ready-made integrations and, recently, also native nodes for the AI Agents (MCP)<\/a>. But be careful: self-hostable doesn't mean mandatory<\/em> to install yourself. There's also a cloud version. If you don't have anyone to manage a server, start with the cloud and think about self-hosting later, when it makes sense for data and costs.<\/p>\n\n Here's a distinction that will save you mistakes.\u2019Simple automation<\/strong> It's a linear chain: "If A happens, then do B." You get a form, save it to a spreadsheet. That's it. For things like this, you sometimes don't even need n8n.<\/p>\n One structured workflow<\/strong> It\u2019s different: it has more steps, makes decisions (\u00abif the customer is already in the CRM, do this; otherwise, do that\u00bb), transforms data along the way, and handles the unexpected. This is where n8n really shines. The rule of thumb: if your automation has more than one \u00abif\u00bb and involves multiple tools, you\u2019re in workflow territory, and you\u2019re better off building it in a structured way.<\/p>\n\n Non-theory: things that are actually built in half a day.<\/p>\n Common temptation: putting AI everywhere. It's not necessary. AI makes sense when it comes to interpreting unstructured data.<\/strong>Understanding the subject of an email, summarizing a text, sorting poorly written requests, generating a draft. In those cases, a fixed rule isn't enough.<\/p>\n Where instead a simple rule is enough<\/strong>If the amount exceeds 500 euros, notify the owner. That's a clear \u00abif\u00bb: using AI to decide would be slower, more expensive, and less reliable. Use AI where there's ambiguity, rules where there's a clear threshold. If you want to delve deeper into this boundary, I've discussed it in how to understand if a process can be automated<\/a>.<\/p>\n\n Automation is useful, but not always. There are situations where a workflow complicates your life instead of simplifying it:<\/p>\n The question to ask yourself is not \u00abCan I automate it?\u00bb (almost everything can be), but \u00abIs it worth it?\u00bb. They are two different things.<\/p>\n\n No software, for now. Grab pen and paper and write five repetitive activities<\/strong> of your week: the boring, same-old ones that you do \u00abbecause they have to be done.\u00bb For each, mark down how much time it takes and how \u00abmechanical\u00bb it is. Then choose the simplest and most repetitive<\/strong> \u2014 not the most important. That's your first stream. Start there, get it working well, and only then move on to the next one.<\/p>\n\n n8n isn't magic, and it doesn't give you whole days back out of thin air. It's a solid tool for eliminating, one by one, the repetitive tasks that steal your attention. The value isn't in setting up a hundred automations\u2014it's in setting up just a few of the right ones and keeping them under control.<\/p>\n\n\nSimple automation or structured workflow?<\/h2>\n
The pieces that make up a flow<\/h2>\n
\n
Four concrete examples<\/h2>\n
\n
Where AI makes sense in a workflow (and where it doesn't)<\/h2>\n
When n8n Isn't the Right Answer<\/h2>\n
\n
Common errors<\/h2>\n
\n
The first step, to be taken today<\/h2>\n
The point, in the end<\/h2>\n
Frequently Asked Questions<\/h2>\n\n\n