n8n Complete Guide: Workflow Automation from Zero to Production

What is n8n?

n8n (pronounced “n-eight-n”) is a workflow automation platform that combines the speed of no-code visual builders with the flexibility of full-code development. The name is a numeronym derived from “nodemation” — a fusion of node and automation, with the 8 representing the eight letters between the first and last “n”.

Think of it as Zapier or Make.com, but self-hostable, developer-friendly, and with native AI agent capabilities built in.

Why n8n Over Zapier or Make?

The key difference: Zapier and Make charge per step/operation. A workflow with 10 steps costs 10 tasks. n8n charges per execution (one complete workflow run) regardless of how many steps it has. Self-hosted n8n Community Edition is free with unlimited executions.

What n8n is Good For

• Automating repetitive tasks — sync data between apps, send notifications, process files
• API orchestration — connect multiple APIs into complex multi-step workflows
• AI agent workflows — build RAG chatbots, autonomous agents, and AI-powered automations
• Data pipelines — ETL operations, data transformation, database syncing
• DevOps automation — CI/CD triggers, infrastructure monitoring, alerting
• Business operations — lead processing, email campaigns, CRM sync, reporting

Who Uses n8n?

n8n is designed for technical users — developers, DevOps engineers, sysadmins, and technically-minded power users. You don’t need to be a developer to use it, but comfort with JSON, basic JavaScript, and API concepts will take you much further.

Pricing: n8n Cloud vs Self-Hosted

n8n Cloud (Hosted by n8n)

What counts as an execution? One complete run of a workflow from start to finish. It doesn’t matter how many steps/nodes the workflow has — a 1-node workflow and a 50-node workflow both count as 1 execution.

Self-Hosted

Key insight: The Community Edition is remarkably capable. It has all 400+ integration nodes, AI agent nodes, code nodes, webhooks — everything you need to build production automations. The paid tiers are mainly about team collaboration, SSO, and enterprise governance, not about unlocking core automation features.

Cost Comparison at Scale

Bottom line: Self-hosting n8n on a $5-10/month VPS gives you unlimited automations that would cost hundreds or thousands per month on Zapier.

Deployment: How to Host n8n

Hosting Options Overview

Option 1: n8n Cloud (Easiest)

Sign up at n8n.io/cloud. No server, no setup. Choose a plan, get a URL, start building. Data stored in EU (Frankfurt, Germany).

Pros: Zero maintenance, automatic updates, managed infrastructure Cons: Monthly cost, data not on your infrastructure, execution limits

Option 2: Docker Compose (Recommended for Self-Hosting) ⭐

This is the sweet spot — full control, production-ready, with PostgreSQL for the database and Traefik for automatic SSL.

Prerequisites

• A Linux server (VPS or local machine)
• Docker and Docker Compose installed
• A domain name with DNS access

Step-by-Step

1. Install Docker and Docker Compose:

# Verify Docker is installed
docker --version
docker compose version

2. Set up DNS:

Create an A record pointing your subdomain to your server’s IP:

3. Create project directory and .env file:

mkdir n8n-compose
cd n8n-compose
mkdir local-files

Create a .env file:

# Your domain
DOMAIN_NAME=example.com
SUBDOMAIN=n8n
# Result: https://n8n.example.com

# Timezone (affects cron schedules)
GENERIC_TIMEZONE=Australia/Melbourne

# Email for SSL certificate
SSL_EMAIL=you@example.com

4. Create compose.yaml:

services:
  traefik:
    image: "traefik"
    restart: always
    command:
      - "--api.insecure=true"
      - "--providers.docker=true"
      - "--providers.docker.exposedbydefault=false"
      - "--entrypoints.web.address=:80"
      - "--entrypoints.web.http.redirections.entryPoint.to=websecure"
      - "--entrypoints.web.http.redirections.entrypoint.scheme=https"
      - "--entrypoints.websecure.address=:443"
      - "--certificatesresolvers.mytlschallenge.acme.tlschallenge=true"
      - "--certificatesresolvers.mytlschallenge.acme.email=${SSL_EMAIL}"
      - "--certificatesresolvers.mytlschallenge.acme.storage=/letsencrypt/acme.json"
    ports:
      - "80:80"
      - "443:443"
    volumes:
      - traefik_data:/letsencrypt
      - /var/run/docker.sock:/var/run/docker.sock:ro

  n8n:
    image: docker.n8n.io/n8nio/n8n
    restart: always
    labels:
      - traefik.enable=true
      - traefik.http.routers.n8n.rule=Host(`${SUBDOMAIN}.${DOMAIN_NAME}`)
      - traefik.http.routers.n8n.tls=true
      - traefik.http.routers.n8n.entrypoints=websecure
      - traefik.http.routers.n8n.tls.certresolver=mytlschallenge
      - traefik.http.services.n8n.loadbalancer.server.port=5678
    environment:
      - N8N_HOST=${SUBDOMAIN}.${DOMAIN_NAME}
      - N8N_PORT=443
      - N8N_PROTOCOL=https
      - NODE_ENV=production
      - GENERIC_TIMEZONE=${GENERIC_TIMEZONE}
      - N8N_ENCRYPTION_KEY=your-random-64-char-string-here
    volumes:
      - n8n_data:/home/node/.n8n
      - ./local-files:/files

volumes:
  n8n_data:
  traefik_data:

5. Generate an encryption key:

openssl rand -hex 32

Add the output to your .env file as N8N_ENCRYPTION_KEY.

⚠️ Critical: Save this key somewhere safe. If you lose it, all stored credentials become permanently undecryptable after a restart.

6. Start n8n:

docker compose up -d

7. Access n8n:

Navigate to https://n8n.example.com and create your admin account. Done!

Option 3: Docker Compose with PostgreSQL (Production) ⭐⭐

For production workloads, replace the default SQLite with PostgreSQL for better performance and reliability. Add this to your compose.yaml:

  postgres:
    image: postgres:16-alpine
    restart: always
    environment:
      - POSTGRES_DB=n8n
      - POSTGRES_USER=n8n
      - POSTGRES_PASSWORD=your-strong-password
    volumes:
      - postgres_data:/var/lib/postgresql/data

  n8n:
    # ... same as above, plus:
    environment:
      - DB_TYPE=postgresdb
      - DB_POSTGRESDB_HOST=postgres
      - DB_POSTGRESDB_PORT=5432
      - DB_POSTGRESDB_DATABASE=n8n
      - DB_POSTGRESDB_USER=n8n
      - DB_POSTGRESDB_PASSWORD=your-strong-password
    depends_on:
      - postgres

volumes:
  n8n_data:
  traefik_data:
  postgres_data:

Option 4: Quick Local Docker (Testing)

For local testing without SSL or a domain:

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

Then open http://localhost:5678.

Key Concepts: How n8n Works

The Building Blocks

How Data Flows

Trigger Node → Node A → Node B → Node C → Output
     ↓             ↓          ↓          ↓
  Starts the   Receives   Receives   Receives
  workflow     items      items      items
               from A     from B     from C

Each node receives items (JSON objects) from the previous node, processes them, and passes results to the next node. A single execution can process multiple items — if a trigger receives 10 emails, the workflow runs 10 times through the pipeline.

Node Types

Expressions

Expressions let you dynamically reference data from other nodes. They use the {{ }} syntax:

{{ $json.fieldName }}              → Access a field from current item
{{ $node["NodeName"].json.field }}  → Access data from a specific node
{{ $now }}                          → Current timestamp
{{ $workflow.id }}                  → Current workflow ID

JSON: The Universal Language

n8n is built on JSON. Every item that flows through a workflow is a JSON object:

{
  "name": "John",
  "email": "john@example.com",
  "order_total": 150.00,
  "items": ["widget", "gadget"]
}

Understanding JSON is essential for n8n. If you’re not comfortable with JSON, spend an hour learning the basics — it’ll make everything else much easier.

AI in n8n: Building AI Agent Workflows

n8n has 70+ AI nodes built in, making it one of the most powerful platforms for building AI agent workflows. It integrates natively with LangChain concepts.

AI Node Categories

Example: RAG Chatbot Workflow

Webhook (receives question)
    ↓
AI Agent
    ├── Chat Model: OpenAI GPT-4
    ├── Memory: Postgres (conversation history)
    └── Tools:
        ├── Vector Store (search your documents)
        └── HTTP Request (look up external data)
    ↓
Respond to Webhook (sends answer)

Example: Email Triage Agent

Schedule Trigger (every 5 minutes)
    ↓
Read Emails (IMAP node)
    ↓
AI Agent (classifies each email)
    ├── Chat Model: Claude
    ├── Memory: Window Buffer
    └── Tools:
        ├── Slack (notify team of urgent emails)
        ├── Google Sheets (log all emails)
        └── HTTP Request (create ticket in helpdesk)
    ↓
Move Email to folder (based on AI classification)

Supported AI Providers

Pro tip: Use Ollama with n8n to connect to your local LLM (like the Mac Mini M4 Pro we discussed!). This gives you fully private AI automation with zero API costs.

Environment Variables: The Important Ones

VPS Recommendations for Self-Hosting

Minimum specs: 1 vCPU, 1GB RAM for light workloads (a few workflows, low frequency). 2 vCPU, 4GB RAM for production with PostgreSQL and multiple active workflows.

Common Use Cases

1. Sync Data Between Apps

Schedule (daily at 9am)
    ↓
Read from Google Sheets
    ↓
Transform data (Filter, Set fields)
    ↓
Write to Notion / Airtable / Database

2. Webhook-Triggered API

Webhook (receives POST request)
    ↓
Process payload (validate, transform)
    ↓
Create record in database
    ↓
Send Slack notification
    ↓
Respond to webhook with result

3. Scheduled AI Content Generation

Schedule (every Monday 8am)
    ↓
HTTP Request (fetch this week's news/articles)
    ↓
AI Agent (summarise into newsletter format)
    ├── Chat Model: GPT-4 or Claude
    └── Memory: Window Buffer
    ↓
Send via Email (Gmail / SMTP)
    ↓
Post to Slack

4. Home Automation Bridge

Webhook (from Home Assistant)
    ↓
Switch (based on event type)
    ├── Motion detected → Send Telegram notification + log to Sheets
    ├── Door opened → Send push notification + trigger camera recording
    └── Temperature alert → Adjust thermostat + send email

5. Lead Processing Pipeline

Webhook (from website form)
    ↓
AI Agent (enrich & score the lead)
    ├── Chat Model: Claude
    └── Tools: HTTP Request (lookup company), Calculator (score)
    ↓
Switch (based on lead score)
    ├── Hot lead → Create CRM record + notify sales team in Slack
    ├── Warm lead → Add to email sequence
    └── Cold lead → Log for analytics

Best Practices

Workflow Design

Security

Performance

Backup Strategy

# Backup n8n data volume
docker run --rm -v n8n_data:/data -v $(pwd):/backup \
  alpine tar czf /backup/n8n-backup-$(date +%Y%m%d).tar.gz -C /data .

# Backup PostgreSQL
docker exec n8n-postgres pg_dump -U n8n n8n > n8n-db-backup-$(date +%Y%m%d).sql

Your 30-Day n8n Learning Plan

Week 1: Basics

Week 2: Intermediate

Week 3: AI Workflows

Week 4: Production

Learning Resources

Official Resources

YouTube Courses

Key Documentation Pages

n8n Vocabulary Glossary

Final Thoughts

n8n is the most powerful workflow automation tool available for self-hosters and technical users. It hits a unique sweet spot: visual enough for rapid prototyping, powerful enough for production systems, and flexible enough to handle anything from simple notifications to autonomous AI agents.

The combination of n8n + a local LLM (Ollama) + your self-hosted infrastructure is arguably the most cost-effective and privacy-respecting automation stack available today. Zero per-execution costs, zero API costs for AI, and full control over your data.

Start with the Docker quick start, build a few simple workflows, and work your way up to AI agents. The platform rewards curiosity — every workflow you build teaches you something new about what’s possible.

This guide was compiled from n8n official documentation, community resources, and current deployment practices as of July 2026. n8n version at time of writing: stable 2.29.8. Last updated: July 2026.