Make vs Zapier pricing: what you actually pay at every scale

Make looks cheaper at first glance. The plan prices are lower, the operation counts look generous, and plenty of comparison articles will tell you it’s the obvious budget choice. Then some people actually build on it and find their bill higher than expected. Others save hundreds of dollars per year switching from Zapier to Make. Both experiences are real, and the difference comes down to one thing: understanding how each platform actually counts usage.

This is the pricing breakdown that most comparisons skip. Real numbers, real workflow examples, and the specific scenarios where each platform wins or loses on cost.

The core difference: tasks vs operations

Zapier charges per task. A task is a successful action step in your workflow. The trigger that starts the workflow is free. Filters, formatters, paths, and routing logic are also free. You pay only for the actual work steps, things like adding a row to a spreadsheet, sending an email, or creating a CRM record.

Make charges per operation. An operation is every module execution in your scenario. That includes the trigger check, every data transformation, every filter, every router branch, and every action. Unlike Zapier, Make counts steps that never do anything, including checks that find no new data and filters that stop the workflow from proceeding.

This distinction is where the pricing comparison gets complicated. On paper, Make sells far more units per dollar. In practice, some workflows burn through those units much faster than the headline numbers suggest.

Current plan pricing side by side

Here are the published prices as of 2026, billed annually. Monthly billing adds roughly 20 to 30 percent.

The immediate thing you notice: Make’s Pro plan has the same operation count as Make’s Core plan. What you’re paying more for on Pro is priority execution speed and full execution log search, not more volume. To get more operations in Make, you buy add-on credit packs. As of November 2025, Make charges a 25% markup on add-on operations compared to the per-unit rate on your base plan, so running out and topping up costs more than buying the right plan from the start.

One thing Make added in late 2025 that genuinely helps: operation rollover. Unused operations carry forward for one billing cycle. If you use 7,000 of your 10,000 in January, you start February with 13,000. Zapier doesn’t offer rollover. Tasks expire monthly regardless of usage.

What the same workflow actually costs on each platform

Abstract comparisons are less useful than working through the same scenario on both platforms. Here are three real workflow patterns with actual cost math.

Scenario 1: Simple 3-step workflow
A new form submission triggers an add to HubSpot, followed by a Slack notification. Runs 500 times a month.

On Zapier: 2 tasks per run (trigger is free), so 1,000 tasks per month. Covered comfortably on the Professional plan at $49/month.

On Make with webhooks: 3 operations per run (webhook trigger + 2 actions), so 1,500 operations. Well within the free 1,000 ops tier if using webhooks. Make wins clearly.

On Make with polling (every 5 minutes): 288 trigger checks per day x 30 days = 8,640 empty trigger operations, plus 1,000 action operations = 9,640 total. Right at the edge of the Core plan, and that assumes no other workflows running. Make’s cost advantage evaporates.

Scenario 2: Multi-step workflow with filtering
New Stripe payment, filter to only process payments above $100, create a QuickBooks invoice, send a receipt email, update HubSpot, post to Slack. Runs 1,000 times a month.

On Zapier: Trigger is free, filter is free, 4 action steps = 4 tasks per run = 4,000 tasks/month. Sits on the Professional plan at $49/month.

On Make with webhooks: Webhook (1 op) + filter (1 op) + 4 actions (4 ops) = 6 operations per run = 6,000 operations/month. The filter step costs an operation in Make even though it costs nothing in Zapier. You’ll need to add credit packs or upgrade, landing around $20 to $30/month total. Still cheaper than Zapier.

Scenario 3: AI processing workflow
1,000 new support tickets per month, each going through AI analysis, a sentiment check, a database lookup, response generation, a quality check, and a database update. Six steps per ticket.

On Zapier: 6 tasks per ticket x 1,000 = 6,000 tasks/month. Around $49 to $150/month depending on plan tier.

On Make with webhooks: 6 operations per ticket x 1,000 = 6,000 operations/month, plus Make’s AI module steps consume additional operations when using native AI features. With webhook triggers and HTTP requests to external AI APIs rather than Make’s native AI modules, you stay around $20/month. Use Make’s built-in AI nodes and the operation count rises further.

Where Make’s free plan is genuinely better

Make’s free tier is far more useful than Zapier’s. Make gives you 1,000 operations per month, multi-step scenarios, webhook support, and access to data stores at no cost. Zapier’s free plan caps at 100 tasks, blocks webhooks entirely, and restricts you to single-step Zaps.

For a solo operator testing automation for the first time, Make’s free tier is a real working environment. You can build a 5-step onboarding workflow, a CRM update pipeline, or an invoice reminder sequence and run it meaningfully at low volume without paying anything. Zapier’s free plan is closer to a demonstration mode.

The free tier comparison also tells you something about each platform’s philosophy. Make is betting that you’ll learn the system and stay once you see what it can do. Zapier is betting that you’ll pay quickly just to get past the initial limitations.

Hidden costs worth knowing before you commit

A few pricing details that often catch people off guard on both sides.

Make charges for failed runs. If a scenario fails mid-execution due to an API timeout or error, the operations that ran before the failure still count toward your monthly total. On Zapier, failed tasks are not counted. If you’re running workflows against unreliable third-party APIs, this matters.

Make’s AI modules cost extra operations. Using Make’s native AI modules (connecting to GPT-4 or Claude through Make’s built-in integration) consumes more operations per call than using a standard HTTP request to the same API directly. If you’re doing AI processing at volume, routing through Make’s native modules is more expensive than calling the AI API directly via an HTTP node.

Zapier’s task count doesn’t compound with complexity. Adding a filter, a path split, or a formatter step to a Zapier workflow doesn’t increase the task count. Each of those is free. This means a Zapier workflow can get quite complex without the billing growing. Make’s operation count grows linearly with every module added to the canvas.

Make’s add-on operations carry a markup. If you exhaust your monthly allocation and buy extra operations, Make charges a 25% premium on those compared to the base rate on your plan. Running over budget in Make is more expensive per unit than planning for the right volume from the start.

When Zapier’s pricing actually makes sense

There’s a real case for Zapier on cost, and it’s not just “it’s easier.” For teams running workflows with frequent polling triggers against apps that don’t support webhooks, Zapier’s model can end up genuinely cheaper despite the higher sticker price. Since Zapier doesn’t charge for polling checks that find no new data, a workflow monitoring an inbox every few minutes costs nothing extra in Zapier and a significant amount in Make.

Predictability is also worth something. Zapier’s task count is transparent and consistent. You know what a workflow costs before you build it because the math is simple: count the action steps. Make’s true cost requires factoring in trigger frequency, whether webhooks are available, how many router branches you’re using, and whether you’re running native AI modules or API calls. For finance teams or agency operators who need to forecast costs reliably, Zapier’s simplicity has real value.

Common misconceptions

Misconception 1: “Make is always cheaper than Zapier”
Make can be significantly cheaper when you optimize for webhooks and avoid polling-heavy scenarios. For workflows that rely on polling triggers with apps that don’t support webhooks, Make can end up costing as much or more. The comparison only makes sense after running the actual operation math for your specific workflows.

Misconception 2: “More operations means more value”
Make’s 10,000 operations at $10.59 sounds like a bargain over Zapier’s 750 tasks at $19.99. But a single 5-step Make scenario with polling running once per minute uses over 200,000 operations per month. The unit count only matters after you understand how fast your workflows consume those units.

Misconception 3: “Switching from Zapier to Make always saves money”
Teams with mostly webhook-compatible, complex multi-step workflows usually do save substantially. Teams running simple, frequent polling workflows on apps that don’t support webhooks sometimes end up with a higher bill. Audit your current Zap structures before assuming the switch will reduce costs.

Misconception 4: “Make’s free plan and Zapier’s free plan are comparable”
They’re not close. Make’s free tier includes multi-step scenarios, webhook support, and 1,000 operations. Zapier’s free tier is 100 tasks, single-step only, no webhooks. For anyone evaluating both platforms before spending money, start with Make’s free plan for a realistic sense of what the platform can actually do.

Which one to pick on price alone

If your workflows are multi-step, your trigger apps support webhooks, and you or someone on your team is comfortable doing basic setup: Make is cheaper. Often by a factor of 3 to 5 at medium volume. The savings over a year can be $400 to $700 for a small team, which is real money.

If your workflows rely on polling triggers with apps that don’t support webhooks, you need predictable billing without any optimization effort, or you’re running automations infrequently at low volume: Zapier’s pricing is more predictable and potentially competitive depending on your exact scenario mix.

Pricing is one factor in the full decision. For the complete picture on features, AI capabilities, and which platform fits different team types, the Zapier vs Make vs n8n comparison covers where each platform fits across the full range of automation use cases.