Most developers reach a point where they’re writing the same glue code over and over. Webhook receives data, transform it, send it somewhere else. Poll an API, check a condition, trigger an action. Retry if it fails.
I used to write this code by hand. Express routes, cron jobs, error handling, retry logic. It worked, but it was slow to build and painful to maintain. Then I started using n8n, and I stopped writing glue code entirely.
What n8n Actually Is
n8n is an open-source workflow automation platform. Think Zapier, but self-hosted, with full code access, and no per-task pricing that makes you nervous every time a workflow runs.
The core idea: you build workflows visually by connecting nodes. Each node does one thing — call an API, transform data, send an email, run JavaScript. The visual canvas shows you the data flowing through each step in real time.
What makes n8n different from Zapier or Make is that you can write code anywhere. Every node can be replaced with a JavaScript or Python function. You get the speed of visual building with the power of code when you need it.
182k+ stars on GitHub. Used by teams at Mistral AI, Delivery Hero, and Vodafone. This isn’t a toy.
Why Developers Should Care
Here’s the thing most developers get wrong about automation tools: they dismiss them as “no-code tools for non-technical people.” n8n is the opposite. It’s built for technical teams who want to move faster.
You see the data at every step. Click any node and see the exact input and output. No more console.log debugging across three microservices.
You can self-host it. One docker-compose up and you have a full automation platform running on your infrastructure. Your data never leaves your servers.
The AI integration is first-class. n8n has native nodes for OpenAI, Anthropic, local models, vector stores, and tool-calling agents. Building an AI workflow in n8n takes minutes, not days.
Real Use Cases I Run in Production
1. AI Agent Pipelines
This is where n8n really shines. I build multi-step AI agent workflows that would take hundreds of lines of code to write manually:
- Webhook receives a user request
- AI agent analyzes the intent using Claude or GPT-4
- Agent decides which tools to call (search, database lookup, API call)
- Results get synthesized into a response
- Response is sent back via API or email
n8n handles the orchestration, retries, and error handling. I focus on the prompts and the logic.
2. Data Sync Between Services
Every SaaS app needs to keep data in sync across services. New user signs up? Update the CRM, add to the email list, create a Slack notification, log it to analytics.
In n8n, this is a 5-node workflow that takes 10 minutes to build. In code, it’s an afternoon of writing API calls, handling rate limits, and building retry logic.
3. Scheduled Reports and Alerts
Pull data from multiple sources, aggregate it, format it, send it. I run daily reports that query databases, hit APIs, and generate summaries using AI — all in a single workflow that I can modify visually without deploying code.
4. Webhook Processing
Stripe webhooks, GitHub events, form submissions — any incoming webhook can trigger a workflow. n8n handles the parsing, validation, and routing. You just define what happens next.
Self-Hosting: The Real Advantage
This is the point that matters most. n8n is fully open-source and runs on your infrastructure.
docker run -it --rm \
--name n8n \
-p 5678:5678 \
-v n8n_data:/home/node/.n8n \
n8nio/n8n
That’s it. You have a full workflow automation platform at localhost:5678.
For production, add PostgreSQL for persistence and Redis for scaling:
# docker-compose.yml
services:
n8n:
image: n8nio/n8n
ports:
- "5678:5678"
environment:
- DB_TYPE=postgresdb
- DB_POSTGRESDB_HOST=postgres
- DB_POSTGRESDB_DATABASE=n8n
volumes:
- n8n_data:/home/node/.n8n
postgres:
image: postgres:16
environment:
- POSTGRES_DB=n8n
- POSTGRES_PASSWORD=changeme
volumes:
- postgres_data:/var/lib/postgresql/data
Your workflows, your data, your server. No vendor lock-in. No per-execution pricing.
n8n vs Writing Custom Code
The question every developer asks: “Why not just write it myself?”
Write code when: The logic is core to your product, the workflow is tightly coupled to your codebase, or you need sub-millisecond performance.
Use n8n when: You’re connecting services, the workflow changes frequently, you need visibility into execution history, or a non-developer might need to modify it later.
The honest answer: I use both. My app code handles the product logic. n8n handles everything around it — the integrations, the notifications, the data pipelines, the AI agent orchestration.
When n8n Falls Short
It’s not perfect. Knowing the limitations saves you time.
Complex data transformations are easier in code. If you’re doing heavy data processing, write a function and call it from n8n rather than chaining 20 nodes.
Version control is tricky. Workflows are stored as JSON in the database, not in your Git repo. You can export them, but the workflow isn’t as clean as code reviews on a PR.
Testing is manual. There’s no equivalent of jest for n8n workflows. You test by running the workflow and checking the output. For critical workflows, I still write integration tests in code that verify the end-to-end result.
Learning curve for the AI agent nodes is real. The documentation covers basics, but building sophisticated agent workflows requires experimentation and understanding of how tool-calling works under the hood.
Getting Started
If you’re new to n8n, here’s my recommended path:
- Self-host it locally with Docker. Don’t start with the cloud version — you’ll appreciate the freedom later.
- Build a simple webhook → notification workflow. GitHub push → Slack message. Get comfortable with the UI.
- Add a code node. Transform some data with JavaScript to see how code and visual nodes work together.
- Build an AI workflow. Connect an LLM node, add a tool, and watch an AI agent execute steps in your workflow.
The whole progression takes about 2 hours. After that, you’ll start seeing automation opportunities everywhere.
Key Takeaways
- n8n is an open-source workflow automation platform built for technical teams
- Self-host it on your own infrastructure with Docker — no vendor lock-in
- AI agent workflows are first-class with native LLM, vector store, and tool nodes
- Use it for integrations, data pipelines, and orchestration — not for core product logic
- 182k+ GitHub stars, used by enterprise teams, actively maintained
If you’re still writing custom webhook handlers and cron jobs for every integration, give n8n a try. The time you save on glue code is time you spend building actual features.