Zapier open source alternatives

The one thesis that will save you a week

Zapier's product is not automation. Zapier's product is not thinking about automation. Every open-source alternative on this page will make you think about automation again — servers, retries, credentials, upgrades. That's the whole trade. So the honest question isn't "which is the Zapier clone." It's how much automation-thinking are you willing to do to stop paying per task?

Answer that and the six projects below sort themselves in about a minute.

Why teams are leaving Zapier in 2026

Zapier's pricing model punishes success. You build a good workflow, traffic doubles, and suddenly your $50/mo plan is $250/mo because tasks count linearly. There's no way to run high-volume flows without paying pro-rata for every event.

1. Task metering. Every step in every run counts. A workflow with a filter, a lookup, and an action is 3 tasks per event. Ten thousand events a month puts you on Team minimum.
2. No code without paying up. The Code by Zapier step lives behind higher tiers. Meanwhile n8n lets you drop into JavaScript or Python on any step, on the free self-hosted tier.
3. Data flows through Zapier's servers. Fine for most people. Not fine if you're moving customer PII, financial data, or anything regulated.

"Currently using Zapier to automate a GForm response into a GDoc file. Didn't realize until late that it wasn't free, HAHA. Does n8n or Node-RED do this well with Google apps?" — scoutsfinch, r/selfhosted, Sep 2026

That's the modal Zapier user in 2026. Started free, got billed, is shopping for an escape hatch.

The six that matter

n8n — the safe, obvious answer

n8n (195k stars, pushed within hours) is now the default self-hosted Zapier alternative. 400+ integrations, real workflow branching, a code node that runs JS or Python, and a community large enough that almost every problem you'll hit has a Stack Overflow-style answer.

The license (Sustainable Use License) is not OSI open source, but it is source-available and free for internal self-hosted business use. You can run n8n forever without paying n8n Inc. if you don't resell it or repackage it.

Pick n8n if: you want the biggest ecosystem, you value docs and community over ideological OSS purity, and you don't mind that half the "AI Starter Kit" tutorials on YouTube now assume n8n.

Skip n8n if: you need Apache-2.0 or MIT for compliance reasons. The Sustainable Use License disqualifies it for some corporate procurement flows even though 99% of users will never hit its restrictions.

Activepieces — lighter, cleaner, catching up fast

Activepieces (17k stars, actively developed, MIT) is the "we watched n8n get complex and made a simpler thing" answer. The UI is closer to Zapier's step-by-step flow, which matters when you're onboarding non-developers. 280+ pieces as of mid-2026 and growing.

Pick Activepieces if: your users are more "operations person" than "developer" and n8n's node graph looks intimidating to them. Also pick it if MIT license matters to procurement.

Skip Activepieces if: you need a rare integration. n8n's catalog is still 2-3x larger.

Node-RED — the boring 10-year-old that still wins for hardware

Node-RED (20k stars, pushed weekly) predates all of this. Originally IBM. Flow-based programming with a visual editor. If you're doing home automation, MQTT, IoT, or ESP32 stuff — you already know Node-RED. If you're not — you probably don't need it.

Pick Node-RED if: you're wiring together protocols (MQTT, WebSocket, TCP, serial) or automating hardware.

Skip Node-RED if: you want SaaS-style integrations (Slack, Airtable, Notion). It can do them via HTTP nodes but you're building them yourself.

Huginn — for people who want agents, not flows

Huginn (49k stars, pushed regularly) has a different mental model than the rest of this list. You don't build "trigger → action" workflows. You build agents that live on a schedule and check things. Agents chain to other agents.

This shines for monitoring, scraping, RSS-like feed generation, and any workflow that's really "keep an eye on X and tell me when Y changes."

Pick Huginn if: your automations are more watching than reacting — price monitors, availability alerts, personal RSS feeds from sites that killed theirs.

Skip Huginn if: you want the modern Zapier UX. Huginn's UI is functional but firmly from an earlier era.

Windmill — for developers who want workflows as code

Windmill (14k stars, aggressive dev pace) is the developer-first take. Scripts (TypeScript / Python / Go / Bash) are first-class citizens. Flows are typed. It runs Postgres migrations and generates OpenAPI schemas from your scripts. If that sentence sounds like a feature, this is your tool. If it sounds like overhead, it isn't.

Pick Windmill if: you're a Python or TypeScript developer building internal tools and you want workflows in git.

Skip Windmill if: your team isn't developer-heavy. Non-technical users won't love the code-first bias.

Automatisch — the fresh face, still finding its feet

Automatisch (12k stars, moderate pace, AGPL-3.0) is the newest name in the mix. UI is polished, integrations catalog is smaller than the others. Worth trying, worth also checking the pulse before betting a critical workflow on it.

Pick Automatisch if: you want to try something newer and you're not migrating anything critical yet.

Skip Automatisch if: you need a specific integration that isn't in its catalog. The gap versus n8n is real.

Decision framework: pick by who you are, not by feature count

Ops person, not a developer, non-technical team

Pick Activepieces. UX closest to Zapier. MIT license. Non-developers can maintain flows without touching a code editor.

Developer team wiring internal tools

Pick n8n or Windmill. n8n if you want the ecosystem. Windmill if you want workflows in git and typed scripts.

Hardware / IoT / MQTT / home automation

Pick Node-RED. Nothing else on this list is remotely close for wiring protocols and devices.

Monitors, alerts, scrapers, personal information plumbing

Pick Huginn. The agent model fits watching-and-notifying better than any trigger-action tool.

You just want to try something

Pick Automatisch. Low commitment, easy to spin up, easy to abandon if it doesn't click.

Deploy difficulty: what's actually easy vs hard

Every project on this list is nominally self-hostable. That doesn't mean equal effort. Rough guide from our own deploys on a Hetzner CX22:

• Under 30 minutes: Activepieces, Automatisch. Both have single docker-compose files that Just Work.
• 1-2 hours: n8n. Straightforward but you'll want to add a Postgres and set up webhooks with a proper URL.
• 1-2 hours: Node-RED. Trivial to run, real work is in flows.
• 2-4 hours: Windmill. More services, but the docs are excellent.
• Half a day: Huginn. Older stack, less turnkey compose file, but stable once running.

License and commercial-use notes

With a Zapier replacement the license question matters more than most people realise — you're often running these next to customer data or embedding output in a paid product.

• Permissive (Activepieces, Node-RED): MIT / Apache. Embed inside a commercial product without copyleft obligations. Safest for shipping in a proprietary codebase.
• Network copyleft (Automatisch, Huginn, Windmill core): AGPL. The copyleft trigger extends to offering the software over a network — hosting a modified version can oblige you to publish your changes. Read the exact terms before building a paid hosted product on top.
• Source-available, not OSI-open (n8n): Sustainable Use License. Free to self-host for internal business use forever. Not free to resell as a competing hosted product. Fine for 99% of teams; disqualifying for the 1% that want strict OSI-approved licenses only.

License classifications come from the GitHub SPDX field and can lag a relicense. The LICENSE file in the repo is always authoritative.

Cost comparison (rough, honest)

Compare 12 months of Zapier at 20k tasks/month vs self-hosted:

• Zapier Team, 20k tasks/mo: ~$800/year on current pricing
• Zapier Company, high volume: $1,800+/year quickly
• Self-hosted n8n on Hetzner CX22: ~$70/year infra + your time
• n8n Cloud (official): $240/year for the Starter tier if you want managed but not Zapier-priced
• Self-hosted Activepieces on Hetzner CX22: ~$70/year infra + minimal maintenance

Rough rule: budget 2-3 hours a month for updates and small incidents. If that's worth more than $700/year to you, stay on Zapier and stop reading.

Migration tips (imperative, do these in order)

• Export a list of every active Zap. Sort by "how much would I miss this workflow if it stopped tomorrow." Half of Zapier accounts run 5 useful Zaps and 30 abandoned ones. Migrate the 5.
• Rebuild your top 3 workflows in the target tool before moving anything else. If the target can't cleanly express your top 3, it isn't the right tool.
• Run both Zapier and the new tool in parallel for at least 2 weeks. Duplicate side effects are recoverable; missed events are not.
• Rebuild credentials fresh. Do not copy API keys across; rotate them as you migrate. Cheapest security upgrade you'll ever do.
• For anything with money in the loop (payment webhooks, invoicing), keep Zapier as the primary for a full billing cycle after cutover before switching off.
• Log every migrated workflow's first 100 real events and diff against Zapier's task history. This catches the 3 edge cases you didn't remember configuring.
• Cancel Zapier only after 30 days of clean logs on the new tool. Not before.

What you shouldn't do

Don't self-host if you run 3 Zaps. The math never works out. Zapier's free tier or Starter plan is cheaper than your time even at minimum wage. Self-host when volume, cost, or data sensitivity forces it — not for principle.

Don't pick a workflow tool by counting integrations. You'll use 8 of them. Pick by whether those 8 are solid and the code node is easy.

Don't skip the parallel-run period. Every migration horror story starts with "we cut over on Friday."

Frequently asked questions

How long does a real Zapier migration take?

For a team with 10-20 active workflows, budget one week of engineering time plus two weeks of parallel-run before decommissioning Zapier. Rushing past the parallel-run is the #1 source of silent data-loss stories.

Can I run n8n on a $5/mo VPS?

Yes for low volume (a few hundred executions a day). For anything busier, pay for at least 2GB RAM — the Node.js process eats memory when webhooks bunch up. A $6/mo Hetzner CX22 handles a small team comfortably.

What's the biggest hidden cost of self-hosting?

Time you spend debugging a broken webhook at 11pm because the SaaS on the other end silently changed its API. Zapier hides that pain by fixing integrations for you. On self-hosted, you fix them. Budget a few hours a month.

Does n8n's license really let me use it commercially?

Yes, for internal business use. You can automate your company's operations with self-hosted n8n forever without paying anyone. What you can't do is repackage and resell it as a hosted service competing with n8n Cloud. Read the Sustainable Use License in the repo before making any procurement decision on it.

How often is the data on this page refreshed?

GitHub metrics daily. Editorial content at least quarterly, sooner if a project relicenses or ownership changes. The header shows the last revisited date.