It’s 11pm and you’re copying form submissions into a spreadsheet by hand because the Zapier plan that would automate it costs $99 a month, and you’re not sure the ROI is there yet. Or you’re on an ops team that hit the action limit on your current plan mid-month, and now someone has to decide whether to upgrade to the $400 tier or just do it manually until the billing cycle resets.
Neither option feels like a win.
The real problem isn’t that automation is hard. It’s that the tools designed to make it easy are priced in a way that can penalize growth. The more you automate, the more you typically pay; the more you pay, the harder it becomes to justify automating the next thing. That ceiling is artificial, and n8n is one approach to getting out from under it.
What n8n Actually Is
n8n is a workflow automation tool; think Zapier or Make, but one you can run on your own infrastructure. It uses a visual node-based editor where each node represents an action: fetch data from an API, transform it, send it somewhere else. You connect nodes into workflows, set a trigger, and the thing runs.
The hosted version (n8n Cloud) works like any SaaS tool. The self-hosted version runs on a VPS, a Docker container, or whatever you have available. That distinction matters more than it might seem.
Most automation platforms charge per task or per workflow execution. Self-hosted n8n does not. You pay for the server it runs on, not for the number of times it runs. This is a fundamentally different cost model, and it can be advantageous for teams building significant automation volume.
The open-source core is on GitHub, and the community is active. You can inspect what’s happening under the hood. The primary benefit, though, is economic; transparency is secondary.
The Cost Comparison
Let’s examine the pricing structures.
Zapier’s free tier caps at 100 tasks per month, which is useful for testing and not much else. Their Starter plan runs $29.99/month for 750 tasks. The Professional plan, which unlocks multi-step workflows and filters, starts at $73.50/month for 2,000 tasks. If you’re running meaningful automation—lead capture, data syncs, alert routing—you may reach 10,000+ tasks per month without extensive optimization. That puts you at $103.50/month minimum, often more.
A VPS from Hetzner, DigitalOcean, or Vultr with enough headroom to run n8n comfortably costs $5–10/month. The execution count is unlimited. For teams operating at significant scale, this cost structure can offer meaningful savings compared to per-execution pricing models.
Zapier’s onboarding is smoother, and the interface is generally more polished for non-technical users. The support documentation is extensive, and if something breaks, there’s a support team you can contact. For developers and technical ops teams—the people this post is actually written for—the tradeoff often tilts the other way.
Per-seat and per-workflow pricing adds another layer. Many platforms charge based on the number of active workflows or the number of users who can access the tool. Self-hosted n8n has neither constraint. You can run 200 workflows, give credentials to your whole team, and the infrastructure cost typically remains flat. This can matter when you’re scaling business operations and the bottleneck shouldn’t be your automation budget.
Three Workflows Worth Building
Three patterns appear frequently in n8n deployments, and they’re worth understanding concretely.
Lead capture into a CRM with a team notification. A form submission on Tally or Typeform fires a webhook. n8n catches it with a Webhook node, maps the fields, creates a contact in HubSpot (or Notion, or Airtable—there are native nodes for all of them), and posts a formatted message to a Slack channel. The whole workflow is five nodes. On Zapier, this multi-step flow typically requires the Professional plan; on self-hosted n8n, it’s just a workflow.
Scheduled data sync. You have data in a Google Sheet or a Postgres database that needs to push updates to another system on a regular cadence; every hour, every morning at 6am, whatever the requirement is. A Cron node triggers the workflow, a database or Sheets node pulls the data, and a Function node handles any conditional logic before the data goes to its destination. That Function node is where n8n can be particularly useful for developers: you write actual JavaScript, which means you can handle edge cases that no-code tools either can’t touch or hide behind premium tiers.
Internal alert routing. A webhook monitors an API endpoint or payment processor. When a condition is met—a failed charge, an error response, an order above a certain value—the workflow branches. One path tags the customer record; another posts to Slack with relevant context; a third might trigger a follow-up email sequence. This is the kind of glue code that often lives in a Python script on someone’s laptop, maintained by whoever wrote it and potentially forgotten when they leave.
None of these are exotic. They’re automations that ops teams commonly need to run reliably at volume, and they’re where n8n’s node library and code execution capability can make a difference.
The Real Limitations
Self-hosting means someone owns the server. That includes updates when new n8n versions ship, debugging when a node breaks after an upstream API change, and making sure the thing stays up. If you’re comfortable with Docker and basic Linux administration, this is typically a few hours a year. If you’re not, you’ll need to hire or learn; it’s a genuine operational requirement.
n8n Cloud removes that burden but reintroduces per-execution pricing at scale; the math changes depending on your volume.
The UI has a learning curve. It’s more capable than Zapier’s, but it’s also more complex. Non-technical users may struggle with it. That’s not a knock; it’s a design choice that reflects the tool’s priorities.
Community support is active—the forum has regular responses, and the Discord has working engineers in it—but it’s not an SLA. If a workflow fails at 2am and your business depends on it, you’re debugging it yourself or waiting for the community to respond. For mission-critical processes, this is a factor worth considering.
Building a Stack That Holds Up
Starting with n8n is one thing; building an automation stack that holds up as your operation grows is another. The instinct is to build one large workflow that handles everything. Resist it.
Smaller, composable workflows are generally easier to debug, easier to hand off, and easier to modify when requirements change. When you’re deciding whether to chain workflows or split them, use this heuristic: if a failure in one part should stop the whole process, keep it in one workflow. If different parts can fail independently without affecting each other, split them.
Version control can pay off early. n8n lets you export workflow definitions as JSON. Storing those in a Git repository costs nothing and gives you a history of changes, a way to roll back, and a handoff artifact when someone else needs to understand what’s running. This becomes particularly valuable the moment a workflow breaks in production.
If you eventually bring on a team member or contractor, n8n’s credentials management becomes relevant. Credentials are stored separately from workflow logic, which means you can share a workflow without exposing API keys. This separation helps prevent credential leaks and can make onboarding faster.
The n8n benefits that matter at scale aren’t the integrations list or the visual editor; it’s that the tool doesn’t introduce a new cost center every time your automation needs grow. You build the workflow, you own the infrastructure, and the cost structure typically scales with your ambition rather than your billing tier.
Where to Start
Pick one workflow you’ve done manually at least three times this week. Map it as a trigger, a transformation, and an output. Then either spin up n8n’s free cloud trial or provision a $6 VPS, install n8n via Docker, and build just that one thing.
Don’t try to automate everything at once. The best automation stack is the one you’ll actually maintain; that starts with one workflow that works reliably, not ten that sort of work.
Interested in automation & n8n?
We help solopreneurs ship production-ready apps and automate their operations.
Learn About Our QA Services