If you’ve outgrown Zapier’s simple trigger-action automations, or you just want more control over your data and workflows, n8n is worth a serious look. It’s a workflow automation platform that can handle much more complex logic than beginner-friendly tools — and unlike most competitors, the most powerful version is completely free.
Here’s what n8n actually is, what it costs, and how to build your first automation.
What makes n8n different
Most automation tools charge you per task or per “zap.” n8n counts entire workflow runs (executions) instead, and — this is the key detail — you can self-host it for free with unlimited workflows and unlimited executions. You’re only paying for a small server, not for the software itself.
The tradeoff is real: n8n has a steeper learning curve than plug-and-play tools. It’s built for people willing to think in terms of nodes and data flow, not just “when this happens, do that.” If you’re comfortable clicking around and experimenting, that curve is shorter than it sounds.
Cloud vs. self-hosted: what it actually costs
You have two paths into n8n:
- n8n Cloud — fully managed, no setup required. Starter runs about $24/month for 2,500 executions; Pro is about $60/month for 10,000 executions. Good if you want zero technical setup and are willing to pay for that convenience.
- Self-hosted (Community Edition) — completely free software with unlimited executions. You just need a small server, typically $5-12/month, running n8n via Docker. Setup takes about 30-60 minutes if you follow a guide. This is the better deal for anyone even slightly comfortable with basic server setup — you get identical functionality to Cloud for a fraction of the cost.
As of 2026, every n8n Cloud plan also includes unlimited workflows and unlimited users — the only thing that changes between tiers is how many workflow executions you get per month.
Core concepts before you build anything
- Workflow — the overall automation you’re building, made up of connected nodes.
- Node — a single step: a trigger, an action, a condition, or a data transformation. You connect nodes together to build the logic.
- Trigger — what starts the workflow: a schedule, a webhook, a new email, a form submission, etc.
- Execution — one complete run of your workflow from trigger to finish. This is what usage limits are based on.
Building your first workflow
- Pick one repetitive task. Don’t start with your most complex process — start with something small and annoying that you do manually often. A good first project: automatically saving email attachments to a folder, or posting a Slack message when a form gets submitted.
- Add your trigger node. This is the “when this happens” part — a schedule, an incoming webhook, or an app-specific trigger (new row in a spreadsheet, new email, etc.).
- Add action nodes. These are the “then do this” steps. n8n has built-in nodes for hundreds of apps, plus HTTP request nodes for anything that doesn’t have a dedicated integration.
- Test with real data. Use n8n’s built-in execution testing to run the workflow manually before turning it on, so you catch mistakes before they run automatically.
- Activate it. Once it’s working reliably, turn the workflow on and let the trigger run it automatically going forward.
Where n8n starts to shine
The real power shows up once you go beyond simple trigger-action chains: conditional branching (if X, do this; otherwise, do that), looping over data sets, calling AI models directly inside a workflow step, and chaining multiple workflows together so smaller automations feed into larger systems. This is where n8n pulls meaningfully ahead of simpler tools — you’re not limited to one action per trigger, you’re building actual logic.
Is n8n right for you?
- Choose n8n if: you want to automate complex, multi-step processes, you’re comfortable with a bit of a learning curve, and you want to control costs long-term rather than pay per task forever.
- Stick with something simpler if: you just need one or two basic automations and don’t want to touch a server, even a managed one.
Start with self-hosted if you’re at all technical — the cost savings compound fast once you’re running more than a handful of workflows, and you’ll have full control over your own data and infrastructure from day one.