Workflow Automation
Connect the apps you already use and run the glue between them — new signup to CRM, payment to Slack, form to spreadsheet — without writing a backend. Filed as process: these automations are the team's internal plumbing, not code that ships in the product; automations inside your product belong in background jobs or agent tools.
Trends
Public counts each month: pull requests on GitHub, package downloads, stars, Product Hunt followers. They show direction, not market share.
The real choice
Hosted no-code, self-hostable, or code-first. Hosted no-code platforms have the largest app catalogs and the gentlest setup but bill per task or operation, so costs climb with volume. A self-hostable tool runs on your own server for a flat cost and keeps data in-house, but you maintain it. A code-first platform lets you write steps in real code with managed auth, which suits developers but not teammates who don't code. Some self-hostable tools are code-first too.
Pick by situation
Tap the ones that are you — the tools that fit light up below.- Teammates who don't code will build and fix the automations
Zapier - Your flows branch and loop, and you want a lower price per step
Make - You want to self-host with no per-run fees
n8n
Activepieces - You're a developer and want each step written in real code with managed OAuth
Pipedream - Your automations are scripts you already have and you want them scheduled on your own server
Windmill
Compare the tools
Grouped by the side of the choice they answer, not ranked. Open a row for when to use it, the trade-off and what makers say.
ZapierplatformThe widest catalog of app integrations with the simplest trigger-then-action setup, usable by anyone on the team.


103
Use it whenThe apps you need are niche business tools, or non-developers will build the automations.
Trade-offBilled by tasks, and multi-step Zaps need a paid plan; costs rise quickly with high-volume flows.
Used by Aithor, Assembly, Attributer, Badger Maps, Blend and 98 more.
Zapier connects our tools and automates repetitive work like syncing qualification data and routing leads to our CRM. It saves us time and lets us focus on the things that matter most.
MakeplatformMulti-step flows with branches, loops and data mapping on a visual canvas, at a lower price per operation.


21
Use it whenYour automations have more logic than a straight trigger and action.
Trade-offEvery module action uses a credit, so long scenarios burn through them; the canvas takes longer to learn.
Used by Folderly AI, Maynuu, Morningscore, Range, 14 gentle mornings by Small WIns and 16 more.
We’re working toward a native Make integration to enable fully automated enrichment-to-email workflows. Make is key for our no-code power users.
n8nplatform · self-hostableRunning automations and AI agent workflows on your own server with no per-execution fees, dropping into JavaScript or Python when needed.


38★ 207.3k
Use it whenYou're technical, handle data you'd rather keep in-house, or run high volumes.
Trade-offSelf-hosting means you run upgrades and backups; the license is fair-code rather than OSI open source, and the cloud plans bill by execution.
Used by Databox, Folderly AI, Fundable, n8nChat, Nodey and 33 more.
Our entire content automation runs on n8n. Self-hosted on a $6 droplet. The open-source alternative to Zapier that actually lets you build complex workflows without hitting paywalls.
Activepiecesplatform · open sourceA no-code builder with AI agent steps that you can self-host under an MIT-licensed core, or use hosted.No evidence yet★ 25k
Use it whenYou want n8n's self-hosting without the fair-code license, or teammates who don't code will build the flows.
Trade-offA smaller integration catalog than Zapier; governance and team features sit in the paid editions.
No maker's product we track shows it for this yet.
PipedreamplatformWorkflows written as Node.js or Python steps, with managed OAuth and prebuilt triggers and actions for thousands of APIs.No evidence yet
Use it whenYou're a developer who wants the speed of an integration platform without giving up real code.
Trade-offClosed source and hosted only; less approachable for teammates who don't code, and production use moves to paid plans.
No maker's product we track shows it for this yet.
Windmillplatform · open sourceTurning Python, TypeScript, Go or shell scripts you already have into scheduled jobs, multi-step flows and small internal apps on your own server.No evidence yet106.2k/wk−33% vs npm
Use it whenYour automations are really scripts, and you want schedules, retries, logs and a UI around them without a per-run bill.
Trade-offBuilt for developers; self-hosting means running its server and workers, and some features are enterprise-only under an AGPL core.
No maker's product we track shows it for this yet.
Before you choose
Automate a step only after you've done it by hand enough times to know its edge cases. Start with the two or three that save the most time each week, such as routing signups, payments and support forms into one channel. Give every automation an owner and an error notification, because a silently broken Zap looks exactly like a quiet day. Once an automation becomes part of what customers experience, move it into your own code.
- Running automations with no failure alert, so a broken step silently drops signups or payments for weeks.
- Routing a high-volume trigger, like every new row or page view, through a per-task plan, so the bill jumps overnight.
- Connecting every app with one person's personal account, so the automations break when that person leaves or changes a password.
Other options
Real choices most makers here won't need to weigh.
Decided alongside
What the 144 makers' products here chose for their other decisions.