Zapier’s bill went up again, and the internet has an opinion: switch to Make. A quick search turns into 20 open tabs comparing operations, tasks, and credits, none of which agree on units. Before any of that, the question worth answering is simpler — is this a platform problem or a housekeeping problem.
A real migration means rebuilding every zap from scratch on a different platform, with a different execution model and different failure modes. Do it for the wrong reason and the same complaint resurfaces in six months, on a new bill.
The short version: switching to Make makes sense once a workflow is consistently running past roughly 750 to 2,000 Zapier tasks a month on real, necessary webhook or instant-trigger automations, and hitting the next pricing tier every cycle. At that volume, Make’s credit model tends to offer more headroom per dollar. Below that threshold, the fix is usually not a new platform — it’s deleting zaps nobody is using.
Audit Your Zaps Before You Audit Platforms
The fastest diagnostic takes about 10 minutes. Open the Zaps dashboard, sort by task usage over the last 30 days, and look at what’s actually consuming quota.
Three patterns show up constantly in practice:
- Duplicate zaps left running after a project ended, quietly firing on every trigger event
- Test zaps built during setup and never turned off
- Polling triggers checking an idle spreadsheet or table every few minutes, burning tasks whether or not anything changed
A solopreneur running six active workflows but paying for 40 zaps’ worth of task allowance is not being overcharged by Zapier. The bill reflects what’s turned on, not what’s used.
If deleting the dead weight drops usage under the next pricing tier, the pricing was never the problem. One user on r/nocode described the opposite case clearly: “Zapier’s free tier at 100 tasks lasted me about a month; then I paid for the 750 tasks/actions, and it’s been worth it… Tasks I could at least predict and plan around.” That is what a healthy, audited setup looks like — predictable volume matched to a tier, not sprawl disguised as a pricing complaint.
This audit instinct applies beyond automation platforms. Solopreneurs frequently over-optimize a stack — adding a new AI personal CRM tool instead of consolidating the contacts already scattered across three apps — rather than trimming what already exists.
How Zapier and Make Actually Bill You
The two platforms don’t just price differently — they measure differently, and that difference decides who wins at what volume.
Zapier is task-based. One successful action equals one task. Triggers, filters, and failed steps are free. A five-step zap that fires successfully counts as roughly one task for the completed action, not five.
Make is credit-based (the unit was renamed from “operations” to “credits” on November 6, 2025). A standard action typically consumes one credit at a roughly 1:1 ratio. The catch: polling triggers can burn credits on every check cycle, even when nothing in the source has changed.
Zapier’s official pricing page, checked September 2026, lists the Free plan at 100 tasks/month for $0, Professional starting at $19.99/month billed annually for 750 tasks, and Team starting at $69/month billed annually for 2,000 tasks.
Neither vendor’s pricing page answers the actual question, which is how a specific workflow’s shape maps to its billing unit. A user on r/nocode framed the gap directly: “Make’s polling quietly drains your operation count in the background… Sometimes the ‘cheaper’ platform costs more once you account for how its architecture actually bills.” Another, also on r/nocode, put the tradeoff in sharper terms: “Make polling triggers can be sneaky expensive since they count every check as an operation, even if nothing changes… Zapier’s ‘only on trigger’ approach can be more cost-efficient, but Make still wins for heavy automation at scale.”
The Task-Volume Threshold: When to Switch From Zapier to Make
Zapier’s tiers step from 100 to 750 to 1,500 to 2,000 to 5,000 tasks, and price roughly doubles at each jump past the entry tier. The real financial pain hits at the tier boundary — a workflow running 760 tasks a month pays for the full 1,500-task tier just to cover the overage.
Array and loop-heavy zaps make this worse. Iterating over a spreadsheet row-by-row multiplies task consumption fast, and a workflow that looks modest on paper can chew through a monthly allowance in a handful of runs. A user on r/nocode described hitting this wall directly: “the moment your workflow touches an array, zapier becomes unusable at that tier. 750 tasks sounds fine until you iterate over a 30-row sheet and burn through your entire monthly quota in 25 runs. n8n execution-based billing actually protects you on loops.”
Make’s credit system generally provides more room per dollar at similar volume, but the polling gotcha from the section above undercuts that advantage for workflows built on scheduled checks rather than instant webhooks. One user on r/n8n summarized both platforms’ shape bluntly: “Zapier: Still the easiest for simple API-to-API stuff. But the cost per task is insane once you scale. Make: The most visual control, but the learning curve is steep and it can be slow with heavy data.”
Cost self-reports on Make vary by usage pattern and shouldn’t be treated as an official rate card. One user on r/n8n reported: “the default credits are never enough for me… I went with 40k which turns to be somewhere around 60-70usd… if someone’s on a budget - hosting n8n locally is great.”
The threshold, then, is not a clean task number. It is high, steady task volume built mostly on instant or webhook triggers — not scheduled polling, and not array-heavy iteration, both of which distort the math for either platform.
What Actually Breaks When You Migrate 40 Zaps to Make
Nothing ports over automatically. Every trigger, every filter, and every authenticated connection has to be rebuilt from scratch inside Make’s scenario builder, one module at a time.
For a solopreneur with a modest zap count, this is a Saturday. For someone with 40 zaps accumulated over two years, it is a project — and the time cost usually dominates the software cost. One user on r/n8n who went through a similar move summed it up in one line: “Was cheaper for me as far as running costs are. The time it took to set up is probably the biggest cost.”
Running both platforms in parallel during the transition is standard practice, not overcaution. It catches the workflows that silently stop firing because an auth token wasn’t reconnected, or a filter condition got translated slightly wrong.
The math matters here. If switching only saves $15 to $20 a month, a weekend rebuild plus the risk of a silently broken automation is rarely worth it. That math changes fast once the monthly savings clears $50 to $100 and the workflows are simple enough to rebuild cleanly.
When Self-Hosting n8n Makes More Sense Than Either
n8n bills per execution — one workflow run counts as one execution, regardless of how many steps or loop iterations it contains internally. That structure directly protects against the array-blowup problem that inflates Zapier and Make bills alike.
n8n Cloud’s Starter plan is listed at about €20/month on an annual commitment for 2,500 executions, per the official pricing page checked September 2026. The Community Edition is free software, but self-hosting means paying for a VPS — roughly $5 to $10/month — plus the ongoing time cost of updates and maintenance.
One user on r/n8n who moved off Zapier described the shift in concrete terms: “So I was paying $69/mo for Zapier Team… Got fed up and spent a weekend moving everything to self-hosted n8n on a $5 droplet… Savings: about $800/yr. Setup time: a long Saturday.” That is one person’s outcome, not a guaranteed result, but it illustrates the tradeoff shape: lower recurring cost, higher setup and maintenance responsibility.
On where the crossover sits, one user on r/n8n who directly compared the two platforms’ pricing structures reported: “n8n starts beating make on a cost basis when your work flow has greater than 10 steps.” That is one person’s own comparison, not an independent benchmark, but it lines up with the execution-based billing logic — more steps per workflow costs the same on n8n and costs more on Make.
Self-hosting shows up most naturally in stacks that already lean toward automating knowledge work — email triage feeding into an AI chief of staff app, or a comparison like Cora AI vs Fyxer AI for inbox automation — where the automation layer connecting those tools runs constantly enough to justify owning the infrastructure.
Our Take: When to Actually Switch From Zapier to Make
The audit comes first, always. Most “Zapier is too expensive” complaints resolve after 10 minutes of deleting dead zaps, not after a migration project.
Switching to Make is justified when, after that audit, usage still routinely sits near or above 750 to 2,000 tasks a month, and the workload is dominated by webhook or instant triggers rather than polling. n8n is worth considering instead when workflows regularly run 10 or more steps, or loop over arrays — provided the maintenance tradeoff of self-hosting is acceptable.
Staying on Zapier is the right call when real, audited volume is modest, or when the original complaint was sprawl rather than price. Zapier’s predictable, per-task billing also beats Make’s polling gotchas for teams that value knowing the bill in advance over squeezing maximum headroom per dollar.
The broader point holds regardless of which platform wins: two or three automations that run reliably beat 15 tools and a migration project nobody has time to finish.
Frequently Asked Questions
How many tasks per month before Zapier gets more expensive than Make?
There’s no single number — it depends on trigger type and workflow shape, not just volume. As a rough anchor, workflows consistently running above 750 to 2,000 Zapier tasks a month on instant/webhook triggers tend to see Make’s credit model pull ahead on cost per action.
Is Make.com really cheaper than Zapier once you factor in migration time?
Often not, at least in the first few months. Rebuilding every trigger, filter, and connection from scratch takes real hours, and multiple users on r/n8n describe the setup time — not the running cost — as the actual expense of switching.
When does self-hosting n8n make sense for a one-person operation vs. paying for Make?
Once workflows regularly exceed about 10 steps or loop over arrays, n8n’s per-execution billing tends to beat Make’s per-action credit model, per community cost comparisons on r/n8n. The tradeoff is owning server maintenance and updates instead of paying a platform to handle them.
What breaks or has to be rebuilt when migrating Zaps to Make scenarios?
Every trigger, filter, and authenticated connection needs to be rebuilt manually inside Make — nothing imports automatically from Zapier. Running both platforms in parallel during the transition catches workflows that silently stop firing due to a missed reconnection.
Do you actually need a new platform, or just too many zaps?
Most of the time, it’s the zaps. Sorting the Zapier dashboard by task usage and deleting duplicate, test, and abandoned automations resolves the majority of “Zapier is too expensive” complaints without touching a new platform.
The Real Fix Is Fewer Automations, Not a New Platform
The pattern behind most Zapier bill-shock complaints is a zap-sprawl problem wearing a pricing-problem costume. Forty zaps built up over two years, six of them actually doing anything useful, and a bill that reflects the forty.
The next step is mechanical: open the Zapier dashboard, sort by task usage over the last 30 days, and delete anything with no current use. Only after that audit does a platform comparison — Make’s credits, n8n’s per-execution billing, or staying put — become a decision grounded in real numbers instead of a Twitter thread.
The fastest way to cut your automation bill isn’t a new platform. It’s fewer automations.
