The $89/month bill that started it all
In March 2025, we got our Zapier invoice: $89.07 for the Professional plan. That’s $1,068.84 per year to move data between apps. Our team of 5 had 6 active Zaps doing things like routing Typeform responses into Airtable, sending Slack notifications when Stripe payments came in, and creating Monday.com tasks from Gmail labels. Important work? Yes. Worth over a grand a year? We weren’t sure anymore.
So we did what any reasonably frugal, slightly stubborn team would do: we spent a weekend setting up n8n on a $5/month VPS to see if we could kill that Zapier bill entirely.
The short version: we saved $700/year. We also lost a Saturday to a crashed server that nearly cost us a client relationship. n8n is incredible if you’re technically inclined. Zapier is the best $89/month you’ll ever spend if you’re not. Here’s the full story.
What n8n actually is (because most people still haven’t heard of it)
n8n (pronounced “n-eight-n” — the name comes from “nodemation”) is an open-source workflow automation tool. You can self-host it for free, or pay for their cloud version starting at $20/month. It does roughly the same thing as Zapier: when something happens in App A, do something in App B. But the way it does it is fundamentally different.
n8n gives you a visual flow builder that looks more like a developer tool than a consumer product. Nodes connect to other nodes with lines. Each node can be a trigger, an action, or a piece of custom logic. You can branch, loop, merge, filter, and transform data in ways that Zapier simply doesn’t allow without premium add-ons. And because it’s open-source, you can extend it with custom code — actual JavaScript — right inside your workflows.
The self-hosted part is the big draw. Your data stays on your server. There are no task limits. No “you’ve used 75% of your monthly operations” warning emails. You run it, you own it.
That sounds great until you’re the one running it at 11pm on a Saturday trying to figure out why your Docker container keeps restarting. But we’ll get to that.
Our migration: 6 Zaps, 1 weekend, several arguments
We planned the migration for a Saturday in April 2025. Two of us — me and our lead developer — blocked off the full day. The goal: recreate all 6 Zapier workflows in n8n and shut off the Zapier subscription before the next billing cycle.
The first three workflows took two hours. Typeform to Airtable? Built and tested in 20 minutes. Stripe payment to Slack notification? 15 minutes. Gmail to Monday.com task? A bit trickier because of the label filtering, but done in 30 minutes. n8n’s visual builder made these straightforward — honestly more intuitive than Zapier’s builder for anything with conditional logic.
Then we hit workflow #4: a client onboarding sequence that ran through 5 steps. New client signs a contract in DocuSign → creates a project in Monday.com → sends a welcome email via Gmail → creates a Slack channel → populates a Google Sheet with project details. This Zap had been running flawlessly on Zapier for 8 months. For outbound before that contract exists, our Instantly vs Smartlead comparison shows how the sending platforms handle mailbox rotation, replies, and CRM handoff.
The Docker networking issues started here. n8n couldn’t reach our DocuSign webhook from inside the container. Three hours of Stack Overflow, Docker documentation, and increasingly colorful language later, we figured out the network configuration. The fix was a single line in our docker-compose.yml. Finding that line took three hours.
Workflows #5 and #6 went smoother — we’d learned enough by then. By 8pm Saturday, all 6 workflows were running in n8n. We cancelled our Zapier subscription feeling like geniuses.
That feeling lasted about three weeks.
What n8n does better (and it’s not close for these things)
Let’s give credit where it’s due. n8n beats Zapier in several areas that matter:
Cost. This is the big one. Our self-hosted n8n instance runs on a Hetzner VPS for €4.50/month — roughly $5. That’s $60/year versus Zapier’s $1,068/year. The savings: $1,008/year. Even if you use n8n’s cloud version at $20/month ($240/year), you’re still saving $828/year. For a small team, that’s meaningful money.
Unlimited tasks. Zapier’s Professional plan gives you 2,000 tasks/month. We were using about 1,400, which felt fine until we landed a client that doubled our form submissions. Suddenly we were tracking task usage like it was a mobile data plan. n8n self-hosted has no task limits. We ran 12,000 tasks last month and didn’t think about it once.
The visual flow builder is genuinely better. Zapier’s linear “when this happens, do that” interface works for simple automations. But when you need branching logic (if the form says “enterprise,” do X; if it says “startup,” do Y), Zapier’s Paths feature is clunky and limited. n8n’s canvas lets you branch, merge, loop, and filter visually. It’s closer to a programming environment than a consumer tool — and that’s exactly what we needed.
Code nodes for complex logic. Sometimes you need to transform data in ways that no visual builder supports. n8n lets you drop a JavaScript (or Python) node into any workflow and write actual code. We use this to parse CSV attachments, reformat dates between systems, and calculate values that feed into later nodes. On Zapier, you’d need a separate Code step — which works, but feels like an afterthought. In n8n, code is a first-class citizen.
Your data stays on your server. For most people, this doesn’t matter. But if you’re handling client data, PII, or anything subject to GDPR or SOC 2 requirements, knowing your automation data never touches a third-party server is valuable. One of our clients explicitly asked about data residency. With n8n, the answer was simple: it never leaves our server in Germany. With Zapier, the answer would have involved reading their data processing agreement.
What Zapier does better (and why we still pay for it)
Here’s the part of the article where n8n fans get mad at us. Ready?
Zapier has 7,000+ integrations. n8n has roughly 400. This isn’t a small gap — it’s a chasm. Zapier connects to virtually every SaaS tool you’ve ever heard of and hundreds you haven’t. n8n’s integration library is growing fast, but it’s not in the same universe. We had to write custom API calls for two of our workflows because n8n didn’t have native integrations for tools we use. It worked, but it’s more maintenance overhead.
Zapier works while you sleep. Literally. It runs on Zapier’s infrastructure, which has 99.99% uptime. You don’t think about servers, Docker containers, SSL certificates, or memory usage. It just runs. n8n runs on your server. When your server has a bad day, your automations have a bad day. And you’re the one waking up to fix it.
Zero maintenance. No security patches. No Docker updates. No disk space monitoring. No SSL renewals. No “why is the container using 2GB of RAM all of a sudden?” debugging sessions. Zapier handles all of it. We spend roughly 2-3 hours per month maintaining our n8n instance. Over a year, that’s 24-36 hours of maintenance time. At $50/hour, that’s $1,200-1,800 in hidden labor costs — wiping out the savings for a small team.
Customer support. Zapier has live chat, email support, and a massive knowledge base. When something breaks, you can get help. n8n’s community forum is active and helpful, but there’s no SLA, no guaranteed response time, and no one to ping when your production workflows are down at midnight. If you’re not comfortable debugging issues yourself, this is a dealbreaker.
Error handling and reliability. Zapier’s error handling is mature. Failed tasks get retried automatically. You get email notifications when something breaks consistently. There’s a dashboard showing success rates. n8n has error handling features, but they require manual configuration. If you don’t set up error workflows and monitoring yourself, failures happen silently. We learned this the hard way.
The Saturday crash (our failure story)
Three weeks after our migration, on a quiet Saturday afternoon, our n8n server ran out of disk space. The logs had been quietly filling up — we hadn’t set up log rotation. The n8n container crashed. All 6 workflows stopped running.
We didn’t notice. There were no alerts because we hadn’t set up monitoring. Classic.
What we did notice, at 4pm on Saturday, was a text from a new client: “Hey, I signed the contract about 3 hours ago. Should I have received a welcome email by now?”
The client onboarding workflow — DocuSign → Monday.com → Gmail → Slack → Google Sheets — had died mid-execution. The contract was signed. Nothing else happened. No project created. No welcome email sent. No Slack channel. No project sheet. The client was sitting there wondering if they’d made a mistake hiring us.
Panic is the word. I SSH’d into the server, saw the disk space issue, cleared the logs, restarted the container, and manually triggered the workflow. But here’s the thing: the DocuSign webhook had already fired and failed. n8n doesn’t automatically retry failed executions unless you configure it to. So I had to manually re-send the webhook payload, verify each step ran correctly, then email the client apologizing for the delay.
Total downtime: 3 hours and 12 minutes. Total time to fix: 45 minutes. Total time to set up the monitoring that would have prevented it: 20 minutes. We just hadn’t done it.
That next Sunday, we set up Uptime Kuma (free, open-source monitoring), configured n8n’s built-in error workflows to send us Slack alerts on failure, set up log rotation, and added a disk space monitoring script. Problem solved. But the sting of that client text stays with us.
We now run both n8n and Zapier. More on that below.
The hidden costs nobody talks about
We saved $1,008/year on the Zapier subscription. Here’s what that actually cost us:
| Hidden Cost | Time/Money |
|---|---|
| Initial setup (Docker, server config, SSL) | 8 hours |
| Migrating 6 workflows | 10 hours |
| Learning n8n’s interface and quirks | 5 hours |
| Saturday crash recovery + monitoring setup | 4 hours |
| Monthly maintenance (updates, monitoring) | 2-3 hours/month |
| Docker learning curve | 6 hours (YouTube + docs) |
Total setup time: ~33 hours. At $50/hour blended rate, that’s $1,650 in setup cost. Ongoing maintenance: ~30 hours/year. That’s $1,500/year in ongoing time cost.
So the real math isn’t “$60/year vs $1,068/year.” It’s “$60/year + 30 hours of maintenance” vs “$1,068/year + 0 hours of maintenance.” If your time is worth more than $33/hour, the financial savings vanish entirely. If your time is worth $50/hour, you’re losing money on self-hosted n8n.
We still think it was worth it. But not because of the money. It was worth it because n8n’s flexibility let us build automations that Zapier couldn’t handle — or would have charged significantly more for. The cost savings were a bonus. The capability gains were the real win.
Feature comparison table
The honest breakdown — no filler, no “it depends” cop-outs.
| Feature | n8n (Self-Hosted) | Zapier |
|---|---|---|
| App Integrations | ~400 native + custom API calls | 7,000+ |
| Pricing (Self-Hosted) | Free (you pay for hosting) | $19.99-$69.99+/month |
| Pricing (Cloud) | From $20/month | $19.99-$69.99+/month |
| Task/Operation Limits | Unlimited | 750-100,000/month by plan |
| Visual Builder | Canvas-style, branching, loops | Linear with Paths (limited) |
| Custom Code | JavaScript + Python nodes built-in | Code step available, limited |
| Self-Hosting | Yes — that’s the whole point | No |
| Error Handling | Manual configuration required | Automatic retries + alerts |
| Uptime SLA | Your server’s uptime | 99.99% |
| Customer Support | Community forum | Live chat, email, help center |
| Data Residency | Your server, your rules | Zapier’s infrastructure |
| Learning Curve | Steep (2-3 weeks if new to Docker) | Flat (same day) |
| Maintenance Burden | 2-3 hours/month | Zero |
Pricing comparison
Here’s what you’ll actually pay, not what the marketing pages tell you.
n8n Self-Hosted: $0 for the software. $5/month for a VPS (we use Hetzner Cloud CX-11). $0/year for SSL (Let’s Encrypt). Real cost: $60/year. But add 30 hours/year of maintenance time.
n8n Cloud (Starter): $20/month for 2,500 executions. Good for light use. $240/year. No maintenance. Still has execution limits.
n8n Cloud (Pro): $50/month for 10,000 executions. Better for teams with real volume. $600/year.
Zapier (Starter): $19.99/month for 750 tasks. $239.88/year. Too limited for most real workflows.
Zapier (Professional): $49/month for 2,000 tasks. $588/year. This is what we were on. The sweet spot for small teams.
Zapier (Team): $69/month for 2,000 tasks + collaboration features. $828/year. Only worth it if you need shared workflows with permissions.
| Setup | Annual Cost | Task Limit | Maintenance |
|---|---|---|---|
| n8n Self-Hosted | ~$60 | Unlimited | 2-3 hrs/month |
| n8n Cloud Starter | $240 | 2,500/month | None |
| n8n Cloud Pro | $600 | 10,000/month | None |
| Zapier Starter | $240 | 750/month | None |
| Zapier Professional | $588 | 2,000/month | None |
| Zapier Team | $828 | 2,000/month | None |
The cheapest option is n8n self-hosted. The most convenient option is Zapier Professional. The best value depends entirely on how much you value your Saturday afternoons.
Our real recommendations
Technical team with a DevOps mindset: n8n self-hosted, no question. If your team includes someone who’s comfortable with Docker, Linux server administration, and debugging issues from a terminal, self-hosted n8n is absurdly powerful for the price. The unlimited tasks alone make it worthwhile if you’re running any kind of volume. Start here, set up monitoring on day one (don’t skip this like we did), and enjoy the savings.
Non-technical team or solo founder: Zapier. We’re not being patronizing — this is genuinely the right call. Zapier works. You connect accounts, build a workflow in 10 minutes, and never think about it again. The $49-$69/month is cheaper than the time you’d spend learning Docker, debugging server issues, and maintaining a self-hosted instance. Your time is better spent on your actual business.
Team that handles sensitive data: n8n self-hosted. If data residency matters for compliance (GDPR, HIPAA, SOC 2), keeping your automation data on your own server is a significant advantage. One less vendor in your data processing chain. One less audit consideration. This alone justified n8n for one of our clients.
Budget-conscious but not technical: n8n Cloud. You get n8n’s superior flow builder and code nodes without the maintenance overhead. At $20-$50/month, it’s competitive with Zapier and more capable for complex workflows. You lose the self-hosting data advantage but keep the functionality.
Agency running client-facing automations: Both. We know that’s an annoying answer. But it’s the truth. We run critical client-facing workflows on Zapier (client onboarding, payment confirmations, alert systems) because reliability matters more than cost. We run bulk data processing, internal reporting, and high-volume workflows on n8n because cost and task limits matter more than convenience. The combined cost ($49/month Zapier + $5/month VPS) is still cheaper than what we’d pay for Zapier alone at higher task tiers.
The honest bottom line
After 18 months on Zapier and 12 months on n8n, we use both. Zapier handles anything that touches a client directly — because a missed welcome email or a delayed payment notification isn’t worth the $49/month savings. n8n handles everything else: data syncing, bulk processing, internal alerts, scheduled reporting, and anything with complex branching logic that would make Zapier’s Paths feature cry.
If we could only pick one? Zapier. Not because it’s the better tool — n8n is objectively more capable. But because Zapier’s reliability and zero-maintenance approach means our automations run without us thinking about them. An automation platform that requires your attention isn’t fully automated. n8n is the better software. Zapier is the better service.
That said, n8n’s flexibility has let us build automations we never would have attempted on Zapier. Our monthly reporting workflow pulls data from 4 different APIs, transforms it with JavaScript, generates a PDF, and emails it to 12 stakeholders. On Zapier, this would require a Professional plan at minimum and probably a third-party PDF generation tool. On n8n, it’s one workflow with zero additional cost.
For connecting your project management stack, our Asana vs Monday comparison and Monday vs ClickUp deep dive are good starting points. If you’re evaluating other automation options, our Zapier vs Make guide covers the other major player in this space. And for tracking the time you’ll spend maintaining your self-hosted n8n instance (we’re only half joking), our Toggl vs Harvest vs Clockify comparison has you covered.
FAQ
Is n8n really free?
Yes, the self-hosted version is completely free. You download the Docker image, run it on your server, and that’s it. No license fees, no user limits, no task caps. What you pay for is the server to run it on — a basic VPS costs $4-6/month. n8n’s cloud version (managed hosting, no server maintenance) starts at $20/month, which is not free but still cheaper than Zapier for equivalent task volume. The catch with self-hosted isn’t money — it’s time. Setup takes 4-8 hours if you’re comfortable with Docker, longer if you’re not. Monthly maintenance runs 2-3 hours. That time has real value.
Can n8n replace Zapier entirely?
It depends on your integrations. n8n has ~400 native integrations versus Zapier’s 7,000+. If all your apps have native n8n nodes, absolutely — n8n can replace Zapier and do more. But if you rely on niche tools that only Zapier supports, you’ll be writing custom API calls in n8n’s HTTP Request node. That works, but it’s more effort and more maintenance. We replaced 5 of our 6 Zapier workflows with n8n. The 6th — a webhook-based integration with a niche CRM — stayed on Zapier because the n8n version required custom headers and authentication that broke every time the CRM updated their API.
Is n8n harder to learn than Zapier?
Much harder. Zapier’s interface is designed for non-technical users. You pick a trigger, pick an action, map some fields, and you’re done. Total learning time: 30 minutes. n8n’s visual canvas, while excellent, assumes a certain technical comfort level. You need to understand data structures (JSON), API concepts (webhooks, headers, authentication), and basic server administration if you’re self-hosting. Our team took about 2 weeks to feel genuinely comfortable with n8n. It took 20 minutes to learn Zapier. The payoff for learning n8n is real — you can build things Zapier can’t — but the investment is front-loaded.
What happens if my n8n server goes down?
Your automations stop running and nobody tells you — unless you’ve set up monitoring and error alerts. This is the single biggest risk of self-hosting. We recommend setting up Uptime Kuma (free) or a paid monitoring service like Pingdom ($15/month) to watch your n8n instance. n8n also has built-in error workflows that can ping you on Slack or email when something fails. Configure these on day one. Not day 21 like we did. Our Zapier vs Make comparison covers this same reliability question for Make (formerly Integromat) — it’s a tradeoff that comes up in every automation platform decision.
Should I switch from Zapier to n8n in 2026?
Switch if: your Zapier bill exceeds $50/month, you’re comfortable with basic server administration, you need complex branching logic Zapier can’t handle, or data residency matters for your business. Don’t switch if: your automations are simple and reliable on Zapier, you don’t have anyone on your team who can maintain a server, or your workflows directly impact client experience and downtime isn’t an option. The honest answer for most small teams: try n8n’s cloud version first ($20/month). If you like it and want to save more money, then consider self-hosting. Don’t jump straight to self-hosting like we did — test the waters first.
Prices verified as of April 2026. Both tools update pricing periodically — check their sites for current rates.