跳到正文
DEV Community· ai-saasradar·· 8 小時前AI 評分64

Zapier 與 Make 2026 年定價比較:免費額度數字差 10 倍,估算工作量差 2.5 倍

Zapier vs Make in 2026: 100 tasks against 1,000 credits, a 10x gap in the numbers and a 2.5x gap in the work

AI 導讀

作者根據 2026 年 11 月 22 日查閲的定價頁,比較 Zapier Free 的 100 tasks/月與 Make Free 的 1,000 credits/月;按 Zapier 每次一個 action、Make 每次四個 module 的假設,估算兩者分別可跑 100 次與 250 次。

正文

Zapier vs Make in 2026: 100 tasks against 1,000 credits — a 10× gap in the numbers and a 2.5× gap in the work

Both pricing pages now sell a unit rather than a plan. Zapier counts tasks, Make counts credits, and since 27 August Make has said so explicitly: "each action your scenario performs consumes a certain number of credits — most actions consume 1 credit."

That single sentence is the reason the two free tiers cannot be compared as printed. 100 against 1,000 looks like a tenfold difference. It is not, because the two vendors count different events. Here is each page as it was served on 22 November 2026, then the arithmetic that makes them comparable, then the parts neither page will tell you.

The two ladders as printed

Plan Zapier (monthly billing) Make (annual billing, 10,000 credits)
Free $0 — 100 tasks/month; Zaps, Tables and Forms $0 — 1,000 credits/month; 2 active scenarios; 15-minute minimum interval; 5-minute max run
Entry paid Professional $19.99/month Core $9/month — $0.90 per 1,000 credits; unlimited scenarios; 1-minute interval; 40-minute max run
Mid Team $69/month, up to 25 users Pro $16/month — $1.60 per 1,000; custom variables; full-text log search; priority execution
Top of the public ladder Enterprise (custom) Teams $29/month — $2.90 per 1,000; teams and roles; shared templates
Unit size A 100 → 2M tasks/month selector decides your tier A credits slider decides the allowance; the plan decides the features

First paid month, by vendor unit

Two things jump out of that table before any maths. Zapier's price moves with the task tier, not with the plan name — the page ships a selector from 100 tasks to 2 million and quotes $19.99 and $69 as the anchors. Make's price moves with the plan, and the credit allowance is a separate slider (10,000 was the default the page loaded with).

And on Make, the price per 1,000 credits rises as you climb: $0.90 on Core, $1.60 on Pro, $2.90 on Teams.

Make price per 1000 credits by plan

That is not a mistake. The higher plans are notcheaper volume — they are features (custom variables, log search, priority execution, team roles) attached to the same credits. If you only need more runs, the slider is the lever; if you need a feature, you pay a higher unit price for all of your credits.

The unit definitions, in the vendors' own words

Zapier: "Every step in a Zap and every external connector call uses tasks — though rates may vary. AI model tier, code runtime, and connector type each affect how many tasks an action uses." Tasks are pooled across the account, with no separate budgets per product. A Zapier MCP tool call costs two tasks.

Make: every module action is one credit. The Router and the error-handler modules (Rollback, Break, Resume, Commit, Ignore) cost nothing. The Code app costs two credits per second of execution time.

So the same four-module automation — a trigger, a filter, a transform and a create — spends roughly four credits per run on Make, while Zapier's own wording puts the charge on the action rather than on each module. The number of tasks a given Zap spends is not one per module; the page says it varies with the connector and with AI or code use.

Free plan allowance in each unit

Feed that through the free tiers and the headline changes shape:

  • Make Free: 1,000 credits ÷ 4 modules = 250 runs of a four-module scenario.
  • Zapier Free: 100 tasks. If each run costs one task — the simplest case in Zapier's own description — that is 100 runs.

A tenfold gap in the printed numbers is a 2.5× gap in the work, and it narrows further the moment a run has two actions or an MCP call in it.

Where the units actually bite

Three places, and all of them are in the documentation rather than the pricing card.

  1. Agent-style work. One MCP tool call is two Zapier tasks. Ten tool calls per run is twenty tasks — a fifth of the whole free tier — for a workflow that does nothing but ask an assistant to look something up. On Make, that same pattern spends credits per module plus two credits per second of code, which is a different curve but at least a published one.
  2. Code. Make's Code app is priced by the second of execution: two credits per second. A one-second transform in a scenario that runs 1,000 times a month is 2,000 credits — a fifth of Core's allowance. Zapier's page says code runtime "affects" task usage without printing a rate, so the only way to size it is to build the Zap and watch the counter.
  3. Interval and run length. Make Free caps you at a 15-minute minimum interval and a 5-minute maximum run, with two active scenarios. That is a structural limit, not a volume one: a scenario that needs to fire every minute cannot run on the free plan at any credit count. Zapier's free plan publishes no interval or run-length cap on the pricing page.

What neither page tells you

  1. The conversion rate between the units. Neither vendor publishes "one task equals N credits". Any comparison has to be done per workflow, after counting modules and actions in your own scenario. The 250-versus-100 figure above assumes one action per run on Zapier and four modules per run on Make; change either and the ratio moves.
  2. Whether credits or tasks survive the month. Make is explicit: credits expire at the end of the term, and on Teams and above annual credits last 12 months instead of resetting monthly. Zapier's page does not say what happens to unused tasks at the reset, and the overage path is a switch to pay-per-task billing "at a higher per-task rate than your base subscription tasks".
  3. Monthly prices on Make's page. The page I read had annual billing selected, so $9 / $16 / $29 are the per-month equivalents of an annual commitment, each marked "Save 15%". Zapier's $19.99 and $69 are monthly billing. Comparing the two without adjusting for that would flatter Make by about 15%.
  4. App catalogues. Zapier states integrations for more than 9,000 apps; Make states 3,500+ standard apps plus custom apps on every plan. If the app you need is in one catalogue and not the other, the price comparison is academic.

If you are choosing this week

  • You want the lowest first paid month for a small workflow: Make Core at $9/month (annual) with 10,000 credits is the cheapest entry on either page, and the credits do not depend on the plan name.
  • You need one automation across many apps: Zapier, on catalogue size, at $19.99 for Professional — but size the task tier before you commit, because the selector, not the plan name, sets the bill.
  • You are wiring an assistant into workflows: count the tool calls first. At two tasks per MCP call, Zapier's quota is consumed faster than its headline suggests; on Make the equivalent is module credits plus two per second of code.
  • You are buying for a team: Zapier Team is $69/month for up to 25 users; Make Teams is $29/month plus a credit slider, with roles and shared templates. Those are different products at different prices, and only one of them prices per team rather than per seat.
  • You are on the free tier for real work: Make's free plan is 250 runs of a four-module scenario with a 15-minute floor; Zapier's is 100 tasks with no published interval. The first is more work, the second is more forgiving on scheduling assumptions.

The pair sits side by side with the entry prices and the date each was checked on Zapier vs Make. The single-tool pages for Zapier and Make carry their own records, and if you are weighing a self-hosted option, Make vs n8n and Zapier vs n8n run the same comparison against n8n. The full lists are at Zapier alternatives, Make alternatives and n8n alternatives.

Prices were read from zapier.com/pricing (monthly billing) and make.com/pricing (annual billing selected, 10,000 credits) on 22 November 2026, before tax. The runs-per-month figures are derived from each vendor's own definition of its unit and assume a four-module scenario on Make and one action per run on Zapier; neither vendor publishes a conversion between tasks and credits, and neither figure is a quote for your workflow. Where a page did not state a term — unused task rollover, Zapier's code-runtime rate, Make's monthly-billing prices — this piece says so rather than estimating it.

來源:DEV Community · dev.to