The plain description
N8N is a workflow automation tool. You connect applications together and define what happens when something occurs.
An order arrives in Shopify, so create it in Odoo. A CSV lands, so validate it and import the rows. A WhatsApp message comes in, so understand it, create a ticket and reply.
The idea is not new — Zapier and Make have done this for years.
What makes N8N different is two things: you can run it on your own server, and it does not charge per task.
The node model
An N8N workflow is a set of nodes joined by lines. Each node does one thing.
A trigger node starts it. A schedule, an incoming webhook, a new record somewhere.
Action nodes do the work. Fetch data, call an API, create a record, send a message.
Logic nodes decide what happens next. Branch on a condition. Loop over a list. Merge two paths.
You build by dragging nodes onto a canvas and connecting them.
The whole workflow is visible in one picture. That matters more than it sounds — a colleague can look at it and understand what it does without reading documentation.
FIGURE 1: WHAT A WORKFLOW LOOKS LIKE
Trigger
- Something happens
Fetch
- Get the data you need
Decide
- Branch on a condition
Act
- Create, send, or update
Why self-hosting matters
The feature that defines it.
You can run N8N on your own server. Your workflows, your credentials, and the data flowing through them stay on infrastructure you control.
Three practical reasons that matters:
Data residency. If customer data cannot leave your network, a cloud automation tool is not an option.
Cost at volume. Cloud tools charge per task or per operation. A workflow processing every order, every day, gets expensive. Self-hosted, you pay for the server and the cost does not rise with usage.
Internal systems. Connecting to a database or an application not exposed to the internet is straightforward when the tool runs inside your network.
What it costs you: somebody has to run it. Server, updates, backups, monitoring. That is a real ongoing job. If nobody in your company does this today, the licence saving is not a saving.
N8N also offers a hosted cloud version, which removes that burden.
FIGURE 2: SELF-HOSTED OR CLOUD
Self-hosted
- Data stays on your infrastructure
- Cost does not rise with usage
- Reaches internal systems directly
- You handle updates, backups, monitoring
Cloud
- Nothing to run or patch
- Priced by usage
- Internal systems need exposing or tunnelling
- Someone else handles reliability
What we use it for
Rather than list features, here is the actual work — the shape of it, if not the detail.
E-commerce to ERP. Shopify orders arriving in Odoo automatically, with customers and products matched and duplicates prevented.
Bulk data import. CSV and Excel files validated, batched and loaded into Odoo, with duplicate detection so re-running does not create copies.
Messaging to business system. WhatsApp messages understood by an AI model, turned into structured data, and used to create quotations in Odoo or tickets in Jira — with a confirmation reply going back.
Two-way sync between tools. Jira and Monday.com kept in step, with field and status mapping in both directions.
Scheduled updates. Reference data pulled on a schedule and applied to Odoo with business rules on top.
Provisioning. User accounts created across systems from one action.
The common thread: each of these connects things that had no ready-made integration, and each removes work somebody was doing by hand.
Where it fits
Good fit:
Systems with no ready-made connector. If both have an API, N8N can join them.
Data that cannot leave your network. Self-hosting is the answer.
High volume. Thousands of runs a month, where per-task pricing hurts.
Multi-step logic. Fetch, validate, check for duplicates, transform, create — more than a simple two-app connection.
Poor fit:
A single simple connection. If you just need form submissions in a spreadsheet, use whatever is simplest.
Nobody technical. N8N is friendlier than code and still assumes comfort with APIs and data shapes.
Your business system already does it. Odoo has automated actions, scheduled jobs and approval rules built in. Adding an external tool to do something a setting already covers is a permanent maintenance cost for no benefit.
Check that last one first, every time.
FIGURE 3: BEFORE REACHING FOR N8N
Check your existing systems
- Automated actions and scheduled jobs may already do it.
Check for a ready-made integration
- Many tools already connect natively.
Ask who will maintain it
- Every workflow can break and needs an owner.
Then build
- With a name, a description, and error handling.
What it does not solve
A broken process. If nobody agrees who approves something, automating the routing does not settle it.
Maintenance. Every workflow is something that can break. APIs change, credentials expire, formats shift.
The need for an owner. Undocumented workflows become nobody’s problem until they stop running.
Getting started sensibly
- Pick one small real problem. Not the most complicated one.
- Check whether an existing system already handles it.
- Build it with the cloud trial first — no server to set up while you learn.
- Add error handling so failures are visible rather than silent.
- Name and describe the workflow so somebody else can understand it.
- Decide self-hosted or cloud once you know your real usage.
Point 4 is the one people skip. A workflow that fails silently is worse than no workflow, because everybody assumes it is running.
The short version
N8N connects applications and runs multi-step logic between them, built visually from nodes.
Its distinguishing features are self-hosting and not charging per task. If your data must stay on your infrastructure, or you run high volume, those are the reasons to choose it.
Check what your existing systems already do first. Then build small, handle errors, and give every workflow an owner.
Systems that do not talk to each other?
Get in touch. We build and run n8n workflows connecting Odoo, e-commerce, messaging and project tools — and we check whether a setting already does it first.
