Glossary

What is n8n?

n8n is an open-source workflow automation tool that connects applications through a visual node editor, and which can be self-hosted on your own infrastructure — meaning the workflows and the data passing through them stay under your control.

n8n sits alongside Zapier and Make in the workflow automation category. The characteristic that matters commercially is that it can be self-hosted.

Why self-hosting is the deciding factor

With a hosted-only tool, every record moving through a workflow passes through the vendor's infrastructure. For a business handling patient information, financial detail or anything with a residency requirement, that is a question to answer before anything is built.

Self-hosted n8n runs on infrastructure you choose, in a region you choose. The workflow definitions are files you hold. That answers both the residency question and the exit question in one decision.

What it is good at

  • Connecting things that were not designed to connect. Standard integrations where they exist, HTTP requests where they do not.
  • Being inspected. Each execution is visible step by step, with the data at each stage. When something breaks you can see exactly where.
  • Being handed over. The workflow is a file. It can be exported, versioned and given to someone else to run.

The honest limitations

It is a workflow engine, not an application platform. Complex logic becomes awkward to express and awkward to read, and past a certain point purpose-built code is clearer and cheaper to maintain. Self-hosting also means someone owns updates, backups and uptime — real work, not zero.

Why it comes up in AI projects

Most useful AI systems are mostly not AI. They are a chain of ordinary steps with one or two model calls inside. A workflow tool gives that chain somewhere sensible to live, with the AI as a node rather than as the architecture.

Questions

Do we own the workflows built in n8n?
You should — that is much of the point of choosing it. Workflow definitions can be exported and handed over, so the work is portable to another team or brought in-house without a rebuild.
Is self-hosting difficult?
The initial setup is straightforward. The ongoing part — updates, backups, monitoring — is real but modest work, and it is the trade for keeping data and control in-house.

Related

Wondering whether this applies to your business? That is a thirty-minute call, not a research project.

Book a Consultation Call

Free strategy call

Tell us the number you want moved.

We reply within a day. No spam, no retainer pitch.