Glossary

n8n

n8n is a source-available workflow automation tool, published under a fair-code licence, that connects apps, databases and services so data moves and tasks run automatically, without manual handoffs between systems.

Last updated

Part of our topic guide on AI Skills for Business.

n8n (pronounced "n-eight-n", short for "nodemation") is a source-available workflow automation tool, published under a fair-code licence. It lets you connect different apps, databases and services together so that data moves and tasks run automatically, without someone doing it by hand each time.

What building in it feels like

You build a workflow visually, as a chain of connected "nodes" on a canvas: one node might watch for a new row in a spreadsheet, the next might clean the data, and the last might post it into Slack or a CRM. A run works like this:

  • Trigger: the workflow starts on a schedule, a webhook, or an event in another app (a new email, a form submission, a database change).
  • Nodes: each step in the chain fetches data, transforms it, filters it, branches on a condition, or sends it somewhere else.
  • Connectors: pre-built nodes exist for hundreds of common tools (spreadsheets, databases, email, chat apps, CRMs); a code node covers anything bespoke.
  • Execution: the workflow runs each time its trigger fires, and you can inspect every run to see exactly what data passed through and where, which makes faults easy to trace.

Because the source is available and you're free to self-host, you can run it on your own servers for full control over your data, or use the hosted cloud version if you'd rather not manage infrastructure. The extend-with-code option matters more than it sounds: it's the difference between a tool that stops at its connector catalogue and one that doesn't.

Most data and AI work isn't glamorous model-building. It's the unglamorous plumbing of getting data from one system to another reliably, and n8n sits squarely in that space. Teams adopt it because they're drowning in manual, repetitive handoffs between tools that were never built to talk to each other, and a visual workflow that runs itself is the direct fix.

The tool is not the skill

Our view: the tool is never the hard part. Knowing which process is worth automating, how to design a workflow so it doesn't break, and how to check its output is trustworthy takes real capability, not just access to the software. Most AI and automation initiatives stall on exactly this: the demand side (people who can use the tool well), not the supply side (the tool itself).

That's also why we teach it. Our AI Automation short course uses n8n as its named tool: a learner searching for an "n8n course" is searching for exactly that programme, and we'd rather say so plainly than gesture at "automation tools". The capability the course builds (mapping a process, designing the workflow, checking the output) outlives any one tool; n8n is where you practise it.