What Is n8n? A Beginner-Friendly Guide (2026)

If you've heard people rave about automating their business with n8n but you aren't sure what it actually is, this guide is for you. By the end you'll understand what n8n does, how it works under the hood, how it's priced, how it stacks up against tools like Zapier and Make, and how to build your very first workflow — all in plain English.

What is n8n, exactly?#

n8n is a workflow automation tool. It lets you connect different apps, APIs, databases, and AI models so they work together automatically — without you doing the repetitive clicking, copying, and pasting by hand.

Picture a visual canvas. You drag in "nodes" (building blocks), wire them together with lines, and n8n runs the whole sequence for you — on a schedule, or the instant something happens like a new form submission or an incoming email.

The classic example: a new lead fills out a form on your website. Instead of you manually copying their details into a spreadsheet, adding them to your email list, and pinging your sales channel, n8n does all three the moment they hit submit. That single chain of steps is a workflow, and it can run hundreds of times a day while you sleep.

n8n is also fair-code / source-available, which is a big part of its appeal. You can read the source, run it on your own server for free, and even build custom nodes. That openness is what separates it from fully closed tools and is the foundation of the self-hosted option we cover below.

How n8n works: the mental model#

Once you understand a few core ideas, everything else in n8n falls into place. Every automation is a workflow made of these pieces:

1. Trigger — the event that starts the workflow. It could be a schedule (every morning at 8am), a webhook (an external app pings n8n), a new row in a database, or a new email arriving.
2. Nodes — the steps that do the work. Each node performs one job: call an API, transform data, send a Slack message, run an AI prompt, or filter results.
3. Connections — the lines you draw between nodes. They pass data from one node to the next, left to right.

Data flows through the workflow from the trigger onward, and each node can read the output of the nodes before it. That's the entire model. Once it clicks, the rest is just learning which nodes exist.

Items: how data actually moves#

Here's the one concept beginners most often miss. n8n doesn't pass around a single blob of data — it passes a list of items. An item is a single unit of data, like one contact, one email, or one order. Each item is a JSON object.

If a trigger returns 50 new rows from a database, the next node receives 50 items and runs once per item automatically. You write the logic once, and n8n loops over every item for you. This is why n8n feels effortless at scale: you rarely build loops by hand.

To pull a value out of an item in a later node, you use an expression. For example, to grab the email address from the incoming data, you'd write:

{{ $json.email }}

That {{ ... }} syntax tells n8n "evaluate this and drop the result in here". You can reference fields from any earlier node, do math, format dates, and more. We go deep on this in n8n expressions explained, but the takeaway for now is simple: expressions are how you make data from one step appear in the next.

n8n Cloud vs self-hosted#

n8n comes in two flavors, and choosing between them is one of the first decisions you'll make.

n8n Cloud is the hosted version. You sign up, log in through your browser, and start building. n8n handles servers, updates, backups, and uptime. It's the fastest way to get going and the right choice for most beginners.

Self-hosted means you run n8n on your own infrastructure — a small cloud server, a home machine, or a container platform. It's free to use (you only pay for the server) and gives you total control over your data and configuration. The tradeoff is that you're responsible for setup, security, and updates.

Spinning up a self-hosted instance can be as simple as one Docker command:

docker run -it --rm \
  --name n8n \
  -p 5678:5678 \
  -v n8n_data:/home/node/.n8n \
  docker.n8n.io/n8nio/n8n

Then you open http://localhost:5678 in your browser and you're running n8n. For a real deployment you'd add a domain, HTTPS, and a database, but this shows how low the barrier is. A budget VPS from a host like Hostinger or DigitalOcean is plenty to start.

Not sure which fits you? Our full breakdown lives at n8n Cloud vs self-hosted. A common path is to start on Cloud, learn the ropes, then migrate to self-hosted once volume grows.

Pricing: per-execution, not per-task#

This is where n8n quietly wins, and it's worth understanding before you compare tools. n8n charges by execution — one full run of a workflow — rather than by individual task or action.

Here's why that matters. Imagine a workflow that receives a lead, enriches it with an API, adds it to a CRM, and posts to Slack. That's four steps.

• On a traditional per-task model (like Zapier's), that single run can count as four billed tasks.
• On n8n's per-execution model, the entire run counts as one execution — no matter how many nodes are inside.

The more steps your workflows have, the more dramatically that gap widens. For anyone building rich, multi-step automations, n8n is usually far cheaper at the same volume.

How n8n compares to Zapier and Make#

All three connect apps, but they sit at different points on the power-versus-simplicity spectrum.

In short: Zapier is the smoothest on-ramp for simple, two-step automations. Make offers a nice visual canvas for moderately complex flows. n8n goes furthest on flexibility, code, AI, and cost control — especially once your automations get sophisticated. For the detailed comparisons see n8n vs Zapier and n8n vs Make.

Who is n8n for, and what can you build?#

n8n suits a wide range of people:

• Creators and YouTubers automating content production and publishing.
• Founders and solopreneurs replacing hours of manual busywork.
• Agencies delivering automation as a paid service for clients.
• Developers who want a visual layer over their APIs and scripts.
• Beginners who want a powerful tool that still grows with them.

And a few popular things people build:

• Capture leads from a form, enrich them, add them to a CRM like Airtable, and notify the team in Slack.
• Summarize incoming emails with OpenAI and route them by topic.
• Generate and schedule content drafts automatically.
• Build a Telegram or Slack assistant powered by an AI agent connected to your own data.

For dozens more, see our automation ideas for small businesses.

Build your first workflow: a step-by-step walkthrough#

Let's make something real and simple: when a webhook receives data, send a formatted message to Slack. This teaches triggers, items, expressions, and connections all at once.

1. Create a new workflow. Click "Add workflow" on your canvas. Give it a name like "Lead Notifier".
2. Add a trigger. Click the + button and search for the Webhook node. This gives you a unique URL that any app can send data to. Set the method to POST.
3. Get a test payload. Click "Listen for test event", then send a sample request to that URL (your form tool, or a quick test from your browser/API client). n8n captures the data so you can see its shape.
4. Inspect the output. Open the Webhook node's output panel. You'll see your data as one item of JSON — for example a name and email field. This is the habit from earlier: always look before you build.
5. Add a Slack node. Click + after the webhook, search Slack, and choose the "Send a message" action. You'll be asked to connect your account the first time — n8n stores this securely as a credential. (More on that in n8n credentials explained.)
6. Reference the data with an expression. In the message field, switch to expression mode and write something like:

New lead: {{ $json.name }} ({{ $json.email }})

7. Test it. Click "Test workflow". n8n runs the chain, pulls the name and email from the webhook item, and posts your message to Slack.
8. Activate it. Flip the Active toggle in the top right. Now the workflow runs automatically every time the webhook receives data — no clicking required.

That's a complete, production-shaped automation. Everything more advanced is just more nodes between the trigger and the final action.

Common beginner pitfalls (and how to avoid them)#

A few mistakes trip up almost everyone early on. Knowing them in advance saves hours.

• Forgetting to activate the workflow. Testing runs it once; the Active toggle is what makes it run automatically. If your live automation "isn't firing", check this first.
• Not looking at node output. Build blind and you'll guess at field names. Always open the output panel and confirm the data shape before referencing it.
• Getting expression paths wrong. {{ $json.email }} only works if the current item actually has an email field at the top level. Nested data needs the right path, like {{ $json.body.email }}. Check the output to be sure.
• Confusing test data with live data. A pinned test payload can mask the fact that your live trigger sends a slightly different structure. Re-test with real data before trusting it.
• Skipping error handling. As workflows grow, add an error workflow or an "IF" branch so a single failed API call doesn't silently break everything.
• Mixing up Cloud and self-hosted webhook URLs. Self-hosted instances need a publicly reachable URL for webhooks to work from the outside world.

Should you learn n8n, and what's next?#

If you do anything repetitive with apps and data, learning n8n will pay off quickly. The curve is gentle for basic workflows and scales smoothly as your ambitions grow — the same tool that sends a Slack alert today can run a multi-step AI agent next month.

Grab our free starter checklist to keep yourself on track as you build your first few automations:

Ready to keep going? Here's a sensible path:

• Start with n8n for beginners: how to start automating for a hands-on first project.
• Learn how webhooks work and how credentials work — the two skills you'll use in nearly every workflow.
• Master expressions to make your data flow exactly where you want it.
• Browse the structured Learn hub and the n8n tool page for a complete overview.
• Still deciding if it's the right tool? Read our full n8n review for an honest verdict on its pros, cons, and value.

Pick one small, annoying task you do by hand every week — and automate it this weekend. That first working workflow is the moment n8n finally clicks.