Compared · Make and Zapier checked 21 August 2026 · Pabbly and n8n 22 August · Make polling and billing terms 27 August
Zapier alternatives: three tools, and the billing model decides which
Short answer: the tools are interchangeable on features and wildly different on billing, so the shape of your automations picks the winner, not the price list. Long multi-step workflows go to n8n. Triggers that check constantly and act rarely go to Pabbly. A few short scenarios at modest volume go to Make. And if a niche app is only on Zapier, stay on Zapier — an automation you can't build has no cost advantage.
Where we stand, before you read the recommendations. Of the tools on this page, Make and Pabbly Connect both pay us a commission if you sign up through the affiliate links on their review pages. n8n pays us nothing. Zapier pays us nothing and never can — its partner program is gated behind consultancy certification and closed to publishers.
So the tools we earn from are also the ones we'd have recommended anyway — which is exactly the situation where you should stop trusting a comparison and start checking it. The decision table below is ordered by workflow shape, not by our incentive, and every claim it rests on is published by the vendors themselves. How this works
Most “Zapier alternatives” articles are a list of nine tools with a paragraph each, and they're useless because the tools genuinely do the same job. What separates them isn't features. It's what each one puts on the meter, and that produces bills that differ by an order of magnitude for identical work.
The question: what shape are your automations?
| Tool | What it charges for | Cheapest when |
|---|---|---|
| Zapier | Each successful action step. Triggers, filters, paths and delays are free — but AI steps bill by model tier, and code, MCP and SDK calls share the same allowance | Short workflows, moderate volume, niche apps |
| Make | Every module run, including trigger checks that find nothing | Few scenarios, low volume, infrequent polling |
| Pabbly | Action steps only — like Zapier, but a one-time licence is available. It calls the check itself an operation and doesn't bill for those at all | Polls often, acts rarely. Permanent, predictable use |
| n8n | Whole workflow executions — step count is irrelevant, but a scheduled check is itself an execution | Long, complex workflows. Or self-hosted, at any scale |
Note where that leaves Make: it is the only tool on this page that charges for checks which find nothing. That is the least flattering line in the table, and it belongs to a tool that pays us. It was written before Make paid us anything and it hasn't moved since.
Why people leave Zapier
Almost always cost, and almost always because of the same miscalculation. People estimate their usage by counting Zap runs rather than action steps, and underestimate by three to five times.
The worked example
A Zap with 4 action steps, running 100 times a day, for 30 days. That's 12,000 tasks a month — not 3,000, and nowhere near the 750 the entry plan includes.
And the counting got less forgiving in mid-2026. AI steps no longer cost one task each — they bill by model tier, reported at roughly one, three or five — and AI, code, MCP and SDK calls all draw from the same allowance as ordinary actions. If your Zaps use AI at all, an estimate built from an older guide is low.
There's also a hard stop most people don't know about: overage has billed at around 1.25× your effective rate, with Zaps pausing entirely once you pass three times your included volume until the next cycle. That's a failure mode, not a soft limit. Zapier changed pay-per-task rates for monthly plans in July 2026, so confirm the current terms for your own billing cycle.
The same arithmetic, run against the tools we earn from
It would be easy to cost Zapier's trap precisely and leave everyone else's vague, so here is the equivalent sum for the alternatives — including the two that pay us.
Make meters the check itself. A trigger polling every five minutes runs about 8,640 times a month, and every one of those costs a credit whether or not anything has changed. That is roughly 8,640 of Core's 10,000 credits before a single useful step runs. On the free tier, where scheduled scenarios can't run more often than every fifteen minutes, you still get about 2,880 checks against an allowance of 1,000 — one always-on scenario drains it before the month is half done.
n8n meters the check too, because a scheduled run is an execution like any other: the same five-minute schedule costs about 8,640 executions against Cloud Starter's 2,500. Step count is free on n8n; frequency isn't.
Pabbly is the genuine exception, and it's the one structural advantage of its model: it calls the check an operation, states that operations aren't billed, and charges only when a step does something.
On all four, a webhook trigger sidesteps this entirely where the source app offers one — it fires on the event instead of asking repeatedly. If you take one thing from this page, take that.
What each costs
| Tool | Free tier | Paid from |
|---|---|---|
| Zapier | 100 tasks/mo, two-step Zaps only, no premium apps, no webhooks | $19.99 annual ($29.99 monthly) for 750 tasks |
| Make | 1,000 credits/mo, 2 active scenarios, scheduled runs no more often than every 15 minutes | $12 annual (Core, 10,000 credits, unlimited scenarios); $16 monthly |
| Pabbly | Small task allowance, no card. Pabbly's own free-plan card is inconsistent — its summary says unlimited workflows, its feature list caps you at two workflows of up to two steps | See note — a fixed-allowance plan, an unlimited-tasks plan, or a separate one-time lifetime licence |
| n8n | Self-hosted community edition — unlimited, forever. No free cloud tier, only a trial | Cloud from ~€20 annually (~€24 monthly) for 2,500 executions |
US dollars except n8n, which prices its cloud in euros. Make raised its paid tiers during August 2026 — Core moved from $9 to $12 — so comparisons still quoting $9 are out of date. Note that Make's $12 is the annual rate, billed for the full year with no prorated refunds; the price you can cancel monthly is $16. Zapier's prices are unchanged, but the way it counts tasks moved in mid-2026, which matters more; see the box above. n8n's prices held, but its active-workflow caps are gone — every cloud plan now includes unlimited workflows and users, so execution volume is the only thing that scales your bill, and guides still quoting a five-workflow Starter limit are out of date. Pabbly's dollar figures are deliberately absent: it restructured its plans during 2026, it serves different prices in different regions, and the published third-party figures contradict each other — see the full review, which works the lifetime arithmetic through at every spend level. Make and Zapier re-checked 21 August 2026; Pabbly and n8n 22 August; Make's polling and billing terms 27 August. Confirm on each vendor's own pricing page before you commit.
When to stay on Zapier
One reason, and it's a good one: integration breadth. Zapier connects around 9,000 apps. Make's library is smaller, Pabbly lists roughly 2,000, and n8n around 500.
If a tool in your stack is only on Zapier, the decision is already made and the price is irrelevant — an automation you can't build has no cost advantage. Check that before you migrate anything.
Zapier also has a decade of public documentation and community answers behind it, and a mature support operation — so whatever you're trying to build, someone has usually published the answer already. If your workflows are short and your time is worth more than the difference, staying is a defensible choice. That conclusion earns us nothing and never could, which is rather the point of including it on a page where alternatives we do earn from are listed right below.
But its free plan is a demo, not a tier
100 tasks a month is about three runs a day of one simple automation. The harder limit is structural: free Zaps can only have two steps — one trigger, one action. No branching, no formatting, no chaining. Premium connectors and webhooks are excluded too.
Use it to confirm Zapier connects your specific apps. That's what it's good for.
Picking the alternative
Listed in the order most people should consider them. Make and Pabbly Connect pay us; n8n doesn't. The order was set before either commission existed and hasn't moved since.
Choose Make if you want a hosted tool with nothing to run and a visual canvas that lays a whole scenario out at once, every branch and filter visible rather than stacked in a list. At $16 a month cancellable — $12 if you commit to a year — it is still cheap for 10,000 credits. Watch the trigger polling: as the box above works out, a five-minute schedule can consume most of a Core plan before doing any actual work. Pays us a commission; the affiliate link is on its review page, not here. Full review.
Choose Pabbly Connect if you want off the subscription treadmill entirely. It counts only action steps and sells a one-time lifetime licence. Be careful with the break-even figure you'll see quoted elsewhere: the widely-repeated “around month four” assumes you're replacing a subscription of roughly $87 a month. Against a cheap tool like Make Core, a one-time licence takes closer to two and a half years to pay for itself — the lifetime deal wins against an expensive subscription, not a cheap one. The other trades are weaker error handling and awkward workarounds for complex branching — fine for convenience automation, risky for anything load-bearing, and we said so before it paid us anything — plus a tier lock: Pabbly states a one-time plan can't be upgraded later, so the allowance you buy is the one you keep. Pays us a commission; the affiliate link is on its review page, not here. Pabbly vs Make.
Choose n8n if your workflows are long, or if you're technical enough to run a server. Per-execution billing means a hundred-step workflow costs the same as a five-step one, and the self-hosted edition is genuinely free with no execution ceiling. The costs are the technical knowledge it assumes — you can drop into JavaScript, and on anything intricate you will — and, if you self-host, the provisioning, updates, backups and uptime that become yours. Pays us nothing, and the free self-hosted edition means it never could — and on long workflows it beats both tools above outright. n8n vs Make.
Questions
Which is the cheapest Zapier alternative?
It depends on shape, not volume. Polls often and acts rarely: Pabbly, and it's the only one here that doesn't bill for the check. Long multi-step workflows: n8n. A few simple scenarios: Make, at $16 monthly or $12 if you commit to a year. Anyone who names a single cheapest tool without asking about your workflows is guessing.
Did any of these prices change recently?
All four moved in some way during 2026, and in three cases it was the counting rather than the price. Make raised its paid tiers in August, with Core going from $9 to $12 a month on annual billing. Zapier's prices didn't move, but AI steps now bill by model tier and code, MCP and SDK calls share the same allowance as ordinary actions. n8n's prices held too, but its active-workflow caps were removed, so cloud plans are limited by execution volume alone. And Pabbly restructured its plans outright — the old three-tier subscription ladder is gone. We re-checked Make and Zapier on 21 August and Pabbly and n8n on 22 August, but confirm all four on the vendors' own pages before you commit.
You earn from some of these. Why should I trust the recommendations?
Check them instead — the whole comparison turns on billing mechanics that all four vendors publish, and confirming them takes about five minutes. Then look at what this page tells you to do that costs us: stay on Zapier if it has the app nobody else does, self-host n8n if you want automation that's actually free, don't put load-bearing workflows on Pabbly, and don't believe the month-four break-even figure unless you're replacing something expensive. None of those earn us anything, and the harshest line in the billing table describes Make.
Which of these is easiest to learn?
We don't rate that, and we'd rather say so than guess. Nobody here has built a production workflow in all four, so any ranking would be repeating other people's impressions with our name on it — see how we choose. What we can tell you is factual: Zapier has by far the most public documentation and community answers; Make lays a scenario out visually so every branch is on screen at once; Pabbly's interface is closest to Zapier's step-by-step model; and n8n expects you to be comfortable with a server and, on anything intricate, with JavaScript.
Can I really run automation for free?
Only one of these makes that honest: n8n self-hosted, which has no licence cost and no execution limit. You pay in server costs and your own maintenance time. Note that n8n's cloud has no free tier at all any more, only a trial. Every other free tier here is a trial in disguise. Self-hosted n8n also happens to be the option that earns us the least, which is nothing.
Will my apps be supported?
Check first, always. Zapier's roughly 9,000 integrations is far ahead of Make's library, Pabbly's ~2,000 and n8n's ~500. Mainstream tools are covered everywhere; niche ones often aren't. Verify before paying anything, and especially before a one-time licence.
Why do you review Zapier if it can never pay you?
Because leaving the category leader out would make these comparisons useless. Its partner program is aimed at implementation consultancies, requires certification, and isn't open to publishers. We'd rather say so than quietly omit the biggest tool in the category — particularly on a page where alternatives we list do pay us.
Do I even need an automation tool?
Not until you're running several tools that must stay in sync. Before that it solves a problem you don't have. If you're at the start, an all-in-one platform keeps everything on one database and needs no connector at all.
How to decide today
Take your most important workflow and write down three numbers: how many action steps it has, how often it runs, and how often the trigger checks for something new.
Many steps, run often: n8n. Checks constantly, acts rarely: Pabbly. Few steps, modest volume: Make. A niche app nobody else connects: stay on Zapier and stop reading comparisons.
And whichever you pick, use a webhook trigger instead of a schedule wherever the source app allows one. On three of these four it is the difference between a bill you predicted and one you didn't.
Make and Pabbly Connect both pay us, through affiliate links on their own review pages — the two links above are internal and earn us nothing. n8n pays us nothing. Zapier pays us nothing and structurally never can. Your price is unchanged whichever you choose.