startupsBy HowDoIUseAI Team

How to set up n8n for AI-powered automation (a beginner's walkthrough)

Learn what n8n is, how it beats Zapier on price and flexibility, and how to build your first AI agent workflow step by step.

A customer emails your small business at 3 a.m. asking about a refund. Nobody's awake to answer. By the time you check your inbox at 9, they've already left a one-star review and moved on to a competitor. That gap — the hours between "customer needs something" and "human is available to help" — is exactly where automation earns its keep, and it's exactly where a tool like n8n starts to look less like a nerdy side project and more like a business necessity.

This guide walks you through what n8n actually is, how it stacks up against Zapier and Make, and how to build a real AI agent workflow from scratch — even if you've never touched an automation tool before.

What is n8n and why is everyone talking about it?

n8n (pronounced "n-eight-n") is an open-source workflow automation platform that lets you connect apps, APIs, databases, and AI models together without writing a full application. Think of it as a visual canvas where you drag nodes onto a board, connect them with lines, and each node does one job — send an email, query a database, call an AI model, post to Slack.

What makes it different from most no-code tools is that it's genuinely open-source and self-hostable. You can run it entirely on your own server, or on a laptop, and never send your data through someone else's cloud if you don't want to. At the same time, it has real enterprise backing and a managed cloud option, so it's not just a hobbyist project — it's being adopted by teams that need production-grade reliability.

The AI side of n8n has grown fast. n8n introduced LangChain integration and dozens of AI nodes, and the platform now ships with a dedicated AI Agent node built specifically for connecting language models to tools and data sources.

How does n8n compare to Zapier and Make?

This is the question every small business owner asks before committing to a tool, so here's the honest breakdown.

Zapier is the easiest on-ramp. Zapier is the easiest to start with and the most expensive to scale, since it bills per task and every single action counts. That's fine if you're running a handful of simple zaps, but a ten-step workflow that runs 1,000 times a month burns 10,000 tasks — and that adds up fast.

Make sits in the middle. Make's visual canvas is genuinely pleasant for branching, multi-step logic, and it bills per operation at a lower unit cost, staying under roughly 100 euros a month even at high volume. It's a solid pick if you want more power than Zapier without touching code.

n8n wins on the pricing model itself. n8n uses execution-based billing where one workflow run equals one execution, regardless of how many steps — meaning a 10-step workflow costs 10x less on n8n than on Zapier, which charges per step. And if you self-host, that cost drops even further, since n8n is the only option with true self-hosting and unlimited executions, eliminating per-execution pricing entirely.

The trade-off is technical comfort. n8n offers the most complete integration via its LangChain nodes for sophisticated AI workflows, Make offers direct connectors for OpenAI with good flexibility but fewer advanced capabilities, and Zapier keeps things simple but with fewer customization options. If you're comfortable clicking around a slightly more technical interface, n8n gives you far more control over exactly how your AI agent thinks and acts. If you want zero learning curve, Zapier still wins.

For a deeper side-by-side across pricing, integrations, and AI capability, this is exactly the kind of comparison worth reading alongside a broader roundup of AI workflow automation tools — n8n tends to land as the pick for technical founders and agencies, while Zapier or Make suit teams that never want to see a line of code.

What does the ROI actually look like?

Automation isn't a hype cycle — it's one of the oldest and most reliable ways to get money back on a software investment. The technology has been around for decades, but it's still one of the strongest ways to actually produce ROI. Research from McKenzie found that standard workflow automation alone can deliver returns of 30% to 200% in the first year, with labor cost savings between 25% and 40% — and most small businesses still haven't touched it. That gap is the opportunity: the businesses that automate their repetitive work now are quietly pulling ahead of the ones still answering every email by hand.

Should you use n8n cloud or self-host it?

You have two real paths, and the right one depends on how technical you are and how much you value control versus convenience.

n8n Cloud is the fully managed option. n8n hosts everything, handles updates, and you just log in and build — no servers, no Docker, no DevOps. Pricing starts around $20/month (Starter) for 2,500 executions and goes up to $50-60/month (Pro) for 10,000 executions, with every plan including unlimited users and unlimited active workflows. There's a free trial to test things out before you commit.

Self-hosting means running the free Community Edition on your own infrastructure — a cheap VPS, a home server, or a container platform. The self-hosted Community Edition remains 100% free with unlimited executions, and a basic server to run it on typically costs somewhere in the $3-7/month range. The catch is that you become the sysadmin: you handle updates, SSL certificates, and backups yourself.

The general rule of thumb: if you're not comfortable managing a server and just want to build automations, start with n8n Cloud. If you're technical, expect high execution volume, or care about data privacy and compliance, self-hosting pays for itself within a couple of months.

How do you get n8n installed and running?

Start with the n8n hosting documentation — it's the official source and covers every install path in detail. If you want the zero-maintenance route, just sign up at n8n Cloud and skip straight to building workflows.

If you'd rather self-host, Docker is the recommended method. n8n recommends using Docker for most self-hosting needs since it provides a clean, isolated environment, avoids operating system and tooling incompatibilities, and makes database and environment management simpler. The basic steps:

  1. Install Docker Desktop from docker.com if you don't already have it.
  2. Create a persistent volume so your workflows survive restarts: docker volume create n8n_data
  3. Run the container using the command in n8n's Docker installation guide, which maps port 5678 and mounts your volume.
  4. Open http://localhost:5678 in your browser and create your owner account.

If Docker feels like overkill for testing, you can also try n8n instantly with npx n8n from the command line — no install required, though it's meant for quick experiments rather than production use.

How do you build your first AI agent workflow?

This is where n8n gets genuinely fun. The official AI workflow tutorial walks through this exact process, and it's worth following alongside this summary.

Here's the core idea: by incorporating the AI agent as a node, n8n can combine AI-driven steps with traditional programming for efficient, real-world workflows — simpler tasks like validating an email address don't require AI, whereas complex tasks like processing the content of an email are excellent uses of an AI agent.

To build a simple email-reply agent:

  1. Create a new workflow and add a trigger node — this could be an email trigger, a webhook, or (for testing) a Chat Trigger node that gives you a simple chat interface to talk to your agent.
  2. Add the AI Agent node. The AI Agent node is the core of adding AI to your workflows — select the Add node connector, start typing "AI," and choose the AI agent node to add it.
  3. Connect a chat model. This tutorial uses OpenAI, but you can easily use DeepSeek, Google Gemini, Groq, Azure, and others. Drop in your API key as a credential and pick your model.
  4. Give it tools. Connect a chat model and one or more tools, and the agent decides which tools to call to complete a task — for an email-reply bot, that might be a tool that looks up order status in a database, or one that drafts and sends the reply via Gmail.
  5. Write a system message. This is where you tell the agent its job: "You're a support assistant for [business name]. Answer questions about orders, refunds, and shipping. If you're unsure, flag the email for human review instead of guessing."
  6. Add memory (optional). A Conversation Memory node lets the agent remember earlier messages in a thread, so follow-up questions don't lose context.
  7. Test it by sending a sample email or message through the trigger and watching the agent decide which tool to call and how to respond.

One important nuance from more advanced builders: dropping an AI Agent node into a workflow isn't automatically "agentic." Without tools connected, it's just a chatbot wearing a fancier hat. An n8n AI agent is a workflow built on the AI Agent node, connected to tools so an LLM can read context, call those tools, and pick the next step on its own — without tools, it is just a chatbot in a workflow. The real value comes from giving the agent things to actually do — query a database, hit an API, search your documents — not just things to say.

What should you automate first?

Don't start with your most complicated process. Start with something narrow, repetitive, and low-risk: auto-tagging support tickets, summarizing incoming leads before they hit your CRM, or drafting (not sending) email replies for a human to approve. Get comfortable with how the AI Agent node behaves, then expand into higher-stakes territory once you trust its judgment.

And keep McKenzie's numbers in mind as motivation: the businesses seeing 30-200% first-year ROI from automation aren't doing anything exotic — they're just doing the boring, repetitive parts of their business with a machine instead of a human, freeing that human up for the parts that actually need judgment. n8n just happens to be one of the cheapest, most flexible ways to get there.

The shutter doesn't have to come down at 3 a.m. It just has to be someone else's problem to answer — and that someone can be a workflow you built in an afternoon.