n8n — The Complete Guide
Open-source Zapier — 500+ built-in integrations, self-hosted, unlimited executions
n8n is an open-source workflow automation platform (TypeScript/Node) built by n8n GmbH — a mature German company that raised a Series B — with a visual drag-and-drop interface for building pipelines from 500+ built-in integrations (Slack, Gmail, Postgres, Webhooks, HTTP, OpenAI, AI Agent, Vector Store nodes like Qdrant/Pinecone/Supabase Vector, LangChain, and more). It runs on Docker with PostgreSQL behind it. On my stack, n8n handles business cron jobs (invoicing, content publishing, agent heartbeats) and replaces three separate SaaS products that used to cost ~$80/month. On yours, n8n can be the glue of the entire stack — CRM automation, marketing ops, internal system integrations, or a full replacement for Zapier (Starter $29/mo for 750 tasks, Professional $73/mo for 2,000, Team $103/user/mo) and Make (Core $10.59/mo, Pro $18.82/mo, Teams $34.12/mo).
What this guide covers
n8n — the technical view
Workflow engine + visual interface + 500+ built-in connectors
n8n is an open-source visual automation platform built by n8n GmbH (a mature German company that raised a Series B) — think of it as 'open-source Zapier' that you run yourself on a server, with no cap on how many automations fire each month. Under the hood it has three layers: (1) an execution engine written in Node.js that runs the automations (each one is called a 'workflow' in n8n), (2) a database (PostgreSQL or SQLite) that stores the workflows and execution history, and (3) a polished visual editor in the browser where you drag boxes around and connect them with lines. On my setup n8n is the smart assembly line of the network — about 25 workflows that wire Kami, CrewAI, and Qdrant together with external services like Gmail, Slack, and WhatsApp.
Installing with Docker
VPS + compose = n8n running in 5 minutes
The recommended way to run n8n in production is via Docker with docker-compose — a single file that defines n8n + a PostgreSQL database + a reverse proxy (Caddy or Traefik) that handles HTTPS automatically. The install itself takes a few minutes, and the result is a fully private instance you own — with workflows and unlimited executions, which makes the savings vs. Zapier immediate and substantial.
Key nodes and triggers
20 nodes that solve 90% of the tasks
Even though n8n ships with 500+ built-in nodes (and hundreds more community nodes), the truth is that across all my workflows — 25 of them in production — roughly 20 core nodes recur and solve 90% of the work. Knowing these tools deeply is the difference between building a workflow in half an hour versus a full day of frustration.
Wiring n8n into the agent network
n8n + Delegator + Kami + CrewAI
This is where n8n's real power on my stack kicks in: it isn't just running by itself — it conducts an orchestra of AI agents. Through HTTP Request nodes, a single workflow can call Kami to send a WhatsApp message, CrewAI to generate a Hebrew blog post, and the Delegator to orchestrate a full email campaign — all in one visual flow, with no new backend.
Advanced logic and expressions
IF/Switch, loops, error handling, sub-workflows
Once workflows get serious (more than 10 nodes, failure handling, loops over large lists), the basics stop being enough — and that's where n8n's advanced capabilities come in. Inline JavaScript expressions, loops over batches, sub-workflows for code re-use, and error branches that handle failures gracefully. These are the tools that turn n8n from 'open-source Zapier' into a serious automation conductor.
n8n in production — what you must take care of
backups, monitoring, scaling, security
Once workflows start running critical business processes (invoices, customer reminders, content publishing), n8n stops being a 'nice-to-have' and becomes critical infrastructure. An hour of downtime = customers don't get messages, campaigns don't launch, money leaks away. Here's the checklist to tick off before you get there.
