n8n: Workflow Automation for Teams Who Outgrew Zapier

Zapier works until it doesn't. The moment you need custom data transformation, a non-standard API auth scheme, conditional logic across five branches, or more than a few thousand tasks per month without a bill that scales with volume — you're stuck. Zapier and Make are built for non-technical users making simple connections. n8n is built for developers who want automation power without giving up flexibility.

Visual workflow builder for the easy parts, full JavaScript/TypeScript execution for everything else, 400+ native integrations, native AI agent support with human-in-the-loop approvals, and a self-hosted option that keeps your data and costs under control. 197,000+ GitHub stars — top 50 on all of GitHub.

What n8n is

n8n (pronounced "n-eight-n", short for "nodemation") is a fair-code workflow automation platform. Written in TypeScript, built on Node.js. The license is the Sustainable Use License — free for self-hosting your own automation, source available, but commercial redistribution requires a commercial license. For teams running it internally: free.

n8n GmbH (Berlin) raised a $55M Series B led by Highland Capital — Sequoia's first seed investment in Germany. 100M+ Docker pulls, 200,000+ community members, releases almost daily. Actively developed commercial product with a strong open-source core.

Visual canvas + Code node

Workflows are built on a visual canvas — nodes connected by edges, data flows as JSON. Every node can be tested in isolation: click "Execute Node" to run against real data and inspect the output before wiring it forward. Branching (IF/Switch), merging, looping, waiting, and error handling are first-class primitives.

The Code node gives you full JavaScript or Python execution with access to workflow data:

// Code node — transform data freely
const items = $input.all();
return items.map(item => ({
  json: {
    fullName: `${item.json.firstName} ${item.json.lastName}`,
    domain: item.json.email.split('@')[1],
    isEnterprise: item.json.plan === 'enterprise'
  }
}));

This is the fundamental difference from Zapier. When the pre-built transformation doesn't fit, you write it. No workarounds — just code.

400+ integrations

Built-in nodes cover: GitHub, GitLab, Jira, Linear, Slack, Discord, Telegram, WhatsApp, Gmail, Outlook, Notion, Airtable, Google Sheets, PostgreSQL, MySQL, MongoDB, Redis, AWS (S3, Lambda, SES, SQS), Stripe, HubSpot, Salesforce, Shopify, and hundreds more. The HTTP Request node covers any REST API not in the catalog — full control over headers, auth, body, and pagination.

Community nodes: hundreds more available in the registry, installable in one click on self-hosted. Custom nodes built in TypeScript via the n8n node SDK.

Native AI — agents, RAG, MCP

The AI Agent node connects to any LLM (OpenAI, Anthropic, Ollama, Mistral, Groq, Gemini) and uses other n8n nodes as tools — database lookups, API calls, code execution — in a ReAct loop. AI agents that actually do things, not just generate text.

Human-in-the-loop approvals (2026): add a review step on any AI Agent → tool connection. The agent pauses, sends an approval request via Slack or email, waits, then continues or aborts. The critical safety mechanism for AI agents touching production systems.

MCP support: n8n works as both an MCP client (calling external MCP tools) and MCP server (exposing n8n workflows as MCP tools to other AI systems).

RAG pipelines: vector store nodes (Pinecone, Qdrant, Weaviate, pgvector), document loaders, and embedding nodes built in. Full ingest-chunk-embed-store-query pipeline on the canvas.

Triggers

Webhook (any HTTP method, sync or async), Schedule (cron or interval), 100+ native app triggers, Form trigger (renders a UI form), Chat trigger (routes to AI Agent), Email trigger (IMAP/SMTP), and Manual trigger for testing.

Sub-workflows

Complex automations composed via the Execute Workflow node — call a sub-workflow with input data, get output back. Build reusable components: "send Slack notification", "lookup customer in CRM", "validate lead" — each maintained independently, called from any parent workflow.

Docker Compose deployment

services:
  n8n:
    image: n8nio/n8n:latest
    restart: unless-stopped
    ports:
      - "5678:5678"
    environment:
      - N8N_HOST=${N8N_HOST}
      - N8N_PROTOCOL=https
      - WEBHOOK_URL=https://${N8N_HOST}
      - DB_TYPE=postgresdb
      - DB_POSTGRESDB_HOST=postgres
      - DB_POSTGRESDB_DATABASE=n8n
      - DB_POSTGRESDB_USER=n8n
      - DB_POSTGRESDB_PASSWORD=${POSTGRES_PASSWORD}
      - N8N_ENCRYPTION_KEY=${N8N_ENCRYPTION_KEY}
    volumes:
      - ./n8n-data:/home/node/.n8n
    depends_on:
      - postgres

  postgres:
    image: postgres:16-alpine
    restart: unless-stopped
    environment:
      POSTGRES_DB: n8n
      POSTGRES_USER: n8n
      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD}
    volumes:
      - ./postgres-data:/var/lib/postgresql/data

Key variables: N8N_HOST (your domain), N8N_ENCRYPTION_KEY (generate once, keep it — losing this key means losing all saved credentials), WEBHOOK_URL. Put Traefik in front for HTTPS. Minimum: 1 CPU, 1GB RAM.

For high-volume deployments: queue mode using Redis + multiple worker containers. The main instance handles the UI and triggers; workers pick up execution jobs from the queue and scale horizontally.

n8n vs Zapier

Zapier is the leader for non-technical users — 7,000+ app catalog, simplest onboarding. It charges per task: at 50,000 tasks/month you're paying $299/month. At 100,000 tasks/month, more.

n8n self-hosted: $0 for unlimited executions. For teams at volume, the economics are decisive. For teams who need code, n8n's Code node eliminates whole categories of Zapier workarounds. For data sovereignty, everything stays on your infrastructure.

Zapier wins on: simplicity for non-developers, the 7,000-app catalog depth, managed reliability with no server to run.

n8n vs Make

Make targets the middle ground — powerful visual scenario building, better than Zapier at complex transformations, cheaper at volume (Core plan $9/month for 10,000 operations). n8n's advantages: real code execution vs Make's limited expression language, better AI/agent capabilities, self-hosting. Make wins on UI polish and non-technical accessibility.

Who it's for

Good fit:

• Developers and technical teams who want automation power with code when needed
• High execution volume where Zapier/Make pricing becomes significant
• Data sovereignty requirements — all workflow data on your infrastructure
• AI agents that call APIs, query databases, and take real actions
• DevOps workflows: GitHub webhooks → deployments, alerts → tickets, on-call automation

Not the right fit:

• Non-technical users who need Zapier's simplicity
• Teams needing obscure integrations in Zapier's 7,000-app catalog not covered by n8n's 400+
• Organizations that need zero operational overhead — n8n cloud exists but the self-hosted model is the core value

My take

n8n fills a real gap: automation powerful enough for developers, visual enough for non-developers to understand, and self-hostable for data control and cost management. The 197k stars reflect a tool that genuinely solves a problem better than the alternatives for its specific audience.

The AI agent capabilities with human-in-the-loop are the most interesting development. Give the agent tools and autonomy, require human confirmation before irreversible actions, connect to MCP servers. This is the right architecture for AI automation: capable but controllable. The fair-code license is a non-issue for internal use — just understand it before building a product on top of n8n.