What Is n8n? Workflow Automation, Explained for Small Businesses
n8n connects the apps your business already uses, so work moves from one to the next without copy and paste. What a workflow is, where AI fits, and how to choose between n8n Cloud and running it yourself.
SkillsUSA California State Champion, Information Technology Services (ITS)
6 min read
On this page
Most small businesses run on a handful of apps that don’t talk to each other. A request comes in through the website form, someone reads it, copies the name and address into the job system, checks the calendar and types a reply. None of it is hard. It’s just the same few steps, every day, done by hand.
n8n is one of the tools that can take those steps over. You’ll see it mentioned next to tools like Zapier and Make, and in a lot of AI tutorials. Here’s what it actually is, in plain English, and how to tell whether it fits a business like yours.
The short version
n8n’s own documentation describes it as “a fair-code licensed workflow automation tool that combines AI features with business process automation.” In practice, you build a workflow on a visual canvas: a row of connected boxes, where each box does one thing and hands its result to the next.
It connects to the apps you already use, like email, calendars, spreadsheets, CRMs and chat tools, and it can talk to other web services through their APIs. It isn’t an AI model, and it isn’t an app your customers see. It’s the plumbing that moves work from one system to the next.
How a workflow works
Every n8n workflow has the same shape: something starts it, a few steps work on the data, and something happens at the end.
- A trigger starts it. The docs define a trigger node as the node “responsible for executing the workflow in response to certain conditions”: a new form entry, a new email, a schedule, or a call from another app.
- Nodes do the work. A node is “an entry point for retrieving data, a function to process data, or an exit for sending data.” One node might look up the customer, another might check a condition (“is this a new job?”), another might ask an AI model to sort the request.
- Actions finish it. The last nodes do something in another system: create a record, send a message, update a spreadsheet.
Here’s what that can look like for a small service business. It’s an example of the pattern, not a recipe for any particular setup:
- TriggerNew website formA request comes in
- NodeAI sorts the requestNew job, question or spam
- NodeIF: is it a new job?Only new jobs carry on
- Waits for youApprove the draft jobNothing is saved until you say yes
- ActionCreate job, send replyIn the CRM, then to the customer
n8n can keep a record of each run (an “execution”), so you can open it later and see what came in, what each step did and where it stopped.
Where AI fits, and where a person still decides
n8n can call an AI model as one step in a workflow, for example to read a free-text request and fill in a structured form: what kind of request it is, who it’s from, what they’re asking for. That’s a good job for AI, because the output is easy to check and easy to correct.
What I don’t want is an AI step that quietly changes records or writes to customers on its own. n8n has two built-in ways to keep a person in charge:
- The Wait node pauses a workflow until something happens, such as a set time, a link being opened or a short form being submitted. That’s how a workflow can stop and wait for you to approve a draft before it goes any further.
- Human approval for AI tools. When an AI agent in n8n wants to use a tool, you can require approval first. The workflow pauses and sends the request to a channel such as Slack, Microsoft Teams, Gmail or the n8n chat, showing which tool the AI wants to use and with what details. If you deny it, the action is cancelled.
The rule I build to is simple. The AI sorts and drafts. Anything that changes a record or reaches a customer waits for a person until the workflow has earned trust.
n8n Cloud or self-hosted?
n8n comes in two forms, and this is the biggest decision for a small business.
n8n Cloud is the fully managed version. n8n runs it for you and, in their words, “handles hosting, updates, and scaling.” You sign in, build workflows and pay a subscription. For most small businesses, this is where I’d start.
Self-hosted means you run n8n on your own server or a cloud server you rent. You control where the data lives and how the system is set up. The trade-off is that you “provide and manage infrastructure” yourself, and n8n’s documentation is direct about what that takes: “Self-hosting n8n requires technical knowledge, including: setting up and configuring servers and containers, managing application resources and scaling, securing servers and applications, configuring n8n.” It recommends self-hosting for expert users, and adds that “mistakes can lead to data loss, security issues, and downtime.”
Self-hosting can make sense when data has to stay on hardware you control, or when you already have someone who looks after servers. If nobody in the business patches and backs up a server today, a self-hosted n8n becomes one more system to keep alive.
A note on the license. n8n is “fair-code”: its source code is public and the community edition is free to use, but it’s under the Sustainable Use License, which allows use “for your own internal business purposes” and limits reselling n8n itself. Running your own business’s workflows is the kind of use it allows. n8n’s license FAQ gives examples of what is and isn’t allowed, and license@n8n.io answers questions.
Have a task your team repeats every week? Let’s map it and see whether automating it pays.
Plan my automationWhen n8n is a good fit
n8n tends to fit when:
- the same task comes back every week and touches two or more apps;
- the steps can be written down, with a clear answer for “what happens if this is missing?”;
- you want one place to see every run, including the ones that failed.
It’s a weaker fit when the task happens a few times a year, when one app already has the automation built in, or when every case needs real judgment. Sometimes the right answer is a better form or a spreadsheet change, not a workflow.
What I’d set up from day one
Whether it runs in the cloud or on your own server, a workflow your business depends on needs the same basics:
- Separate credentials. Each connection signs in with its own account or key, limited to what that workflow needs.
- An error workflow. n8n’s Error Trigger node runs a separate workflow when another one fails, with the details of what went wrong. Point it at a person, so a failure turns into a message instead of a silent gap.
- Approval on anything that changes a record or reaches a customer, at least at the start.
- Someone who owns it. A workflow is a small piece of software. When an app on either end changes, it may need attention.
If you’re weighing n8n against an AI assistant with MCP connections, they solve different problems. n8n runs the same steps the same way every time; an assistant helps with requests that vary. Many businesses end up with both. What Is MCP? explains the assistant side, and A Practical First Automation: From Inbox to Booked Job walks through a first workflow step by step.
If you’d like help deciding whether a process in your business is worth automating, and whether n8n is the right tool for it, that’s what I work through with owners on business automation.
Sources
- n8n documentation: what n8n is, and the fair-code license
- Choose your n8n: n8n Cloud and self-hosted
- Docker installation, self-hosting knowledge prerequisites, n8n documentation
- Nodes: workflows, nodes and trigger nodes
- Wait node and Error Trigger node, n8n documentation
- Human-in-the-loop for AI tool calls, n8n documentation
- Sustainable Use License, n8n documentation
- License FAQ, n8n documentation: examples of allowed use, and the licensing contact