What n8n is, and how it differs from Zapier/Make

Why learn this

Think for a moment about how many things you have done at work today that a computer could really have done by itself:

• In the morning you open Slack and paste today's meetings into the team channel one by one, so everyone knows where you are.
• A customer fills in a Google Form, you open the spreadsheet and copy the data across, and you write them a confirmation email while you are at it.
• An email from a VIP customer lands in your inbox and you forward it to the sales manager straight away, in case it gets missed.
• It is the end of the month, so you open the admin pages of three platforms, pull last month's sales figures, paste them into the report in Excel, and screenshot it for your boss.

These four have one thing in common: the rules are fixed, the data is not. The steps are the same every time; only the content inside them changes. That is exactly what automation tools are best at — you tell it the rules once, and after that it runs itself every day. It does not skip anything, it does not forget, and it does not call in sick.

The automation tool the company picked is n8n (pronounced "n-eight-n", short for "nodemation"). This chapter introduces what it is; the 21 chapters that follow walk you through building workflows that really run.

n8n is automation built like Lego

If n8n has to fit in one sentence, it is this — an automation tool built like Lego.

Every Lego building block has a fixed shape and a set of studs, and once you click them together you have a car or a house. n8n works the same way: it comes with hundreds of ready-made building blocks called "nodes", and each one does a single job —

• one is called Gmail and reads the mail you receive;
• one is called Google Sheets and writes a row into a spreadsheet;
• one is called Slack and sends a message to the channel you name;
• one is called Schedule Trigger and gives the workflow a nudge at 8:00 every morning.

Your job is this — drag the building blocks onto the screen and join them with connections. A connection is the direction the data flows in: the mail Gmail reads travels along it to the next building block.

So how is this different from writing code? If you wrote it yourself, you would have to work out how to fetch mail with the Gmail API, which headers to send, and how to parse the JSON that comes back. n8n has already packed all of that into the Gmail building block. All you do is fill in the fields beside it: which account to use, how many recent messages to fetch, and whether to limit it to one sender.

What it can actually do for you

Take the earlier "post the calendar to Slack in the morning" example and translate it into n8n building blocks:

1. The Schedule Trigger building block: a nudge at 8:00 every morning

   This is where the workflow starts. It has one job — when the time comes, it sets everything downstream in motion. You can have it run every hour, at a fixed time each day, at 9:00 every Monday, on the 1st of each month, and so on.

2. The Google Calendar building block: fetch every event for today

   Connect it with your Google account and tell it to fetch every event between 00:00 and 23:59 today. It sends the events (name, time, location) down the connection to the next building block, one at a time.

3. The Slack building block: send the list to the channel you chose

   It catches the list of events from the previous building block, builds one message out of it, and posts it to a channel in your Slack (or sends it to you as a direct message).

Three building blocks and two connections, and "post the calendar automatically every morning" is done. We walk you through doing exactly this, step by step, in Chapter 8. For now, just get a feel for the scale: a workflow is usually three to seven building blocks, and rarely much longer.

n8n vs Zapier vs Make vs Power Automate

n8n is not the only tool that does this kind of work. You have probably heard of, or used, one of the others. This table lays all four out side by side:

The short version: Zapier for the occasional personal connection, n8n when a company runs things at volume. That is why this handbook is in front of you at work today.

Why WoowTech chose n8n

We evaluated Zapier, Make and Power Automate, and settled on n8n. The reasons come down to these:

1. The data stays in-house

   We self-host the Community edition, so n8n runs on our own server. Customer data, internal messages and reports never travel to another company's cloud. That matters for any work that touches customer lists or financial figures.

2. Costs stay predictable

   The Community edition is completely free, with no limit on users, on the number of workflows, or on how often they run. The server cost is a small slice of the IT spend we already had, far below the several hundred to several thousand US dollars a month that Zapier / Make would come to.

3. The widest choice of nodes

   At the source snapshot, n8n’s integrations page and npm ecosystem listed thousands of integrations and hundreds of community packages; those counts change, so check the live catalogs before relying on a total. Where there is no official node, the HTTP Request node can call any REST API (Chapter 4 shows you how to find one).

4. You can write code to fill the gaps

   For data handling too complex for a ready-made node, drop in a Code node (Chapter 20) and write a few lines of JavaScript or Python. That escape hatch is freedom Zapier / Power Automate cannot give you.

5. AI Agent nodes are supported natively

   n8n ships the LangChain family of AI Agent (Chapter 21) nodes — put GPT / Claude straight into a workflow as a node that makes judgment calls, which works well for front-line customer support, classifying data and summarizing reports. They all go through the company LiteLLM gateway, so AI costs are managed and visible in one place.

6. It fits the tools we already run

   WoowTech runs Home Assistant, Podman and k3s. n8n starts with a single Docker/Podman command, and it can greet HA both ways through a webhook (Chapter 22) — HA notices someone in the meeting room, for instance, and asks n8n to open a Meet call.

Where it fits

n8n is particularly good at these kinds of work. If you have something similar on your plate, find your row:

Where it does not fit

To be straight with you, n8n is not the answer to everything. Force it into the situations below and you will regret it:

How to read this book

The 22 chapters are grouped into 7 parts. Read them in order, or pick out the ones you need.

Common worries before you start

Before you touch anything, some of these question marks may be in your head. We answer them here so they do not distract you halfway through.

1. Wouldn't a company Zapier account be better?

   Zapier's UX does hold your hand more, that is true. But take a common marketing-team use case (500 form entries a day × 3 tasks each = 45,000 tasks a month): on Zapier that starts at several hundred US dollars a month on the Team plan at the very least. Self-hosted Woow n8n runs the same volume at a cost of 0. Learning n8n also counts for you personally on a résumé — it is a widely used source-available, fair-code automation platform.

2. I have never written code. Can I do this?

   You can. The first 15 chapters of this book need no code at all. All you have to do is drag nodes with the mouse and type into fields. The Code node in Chapter 20 is an advanced option; even if you never use it, you can still build 80% of the automation you need.

3. Who is responsible when n8n goes down?

   IT runs the platform (server, backups, upgrades). You are responsible for what is inside your workflows — the same way you do not look after the Google Docs servers and simply concentrate on writing the document. If it really does go down, raise a ticket with IT.

4. Can other departments see my workflows?

   It depends where you put them: in your Personal folder only you can see them; in a Workspace they are shared with the team, and everyone in that workspace can view and edit them. Chapter 13 covers where things are stored and who can reach them.

5. If I break something, will I take down a live system?

   n8n gives you two layers of protection: Manual runs and the Active/Inactive switch. While a workflow is Inactive you can test it hundreds of times, and only when you press Activate does it start running on its schedule or from a webhook. The first time you go live, run it manually a few times to check, then switch it to Active.

FAQ