AI Automation Got Pricier by Model Tier — When to Stay, Switch, or Self-Host

You built a Zap that “just summarizes a ticket and updates a sheet.” It felt cheap — one AI step. Then the run history showed fifteen tasks for a single pass, and your monthly task allotment started looking like a burn rate. That is not a bug in your spreadsheet. It is how model-tier pricing works when AI steps multiply tasks and each tool call multiplies them again.

Since mid-2026, automation buyers have had to compare three different meters: Zapier’s task multipliers by model tier, n8n’s full workflow executions, and Make’s credits (sometimes token-dynamic for AI). The decision is not “which logo is trendy.” It is stay and tune, switch billing models, or self-host and pay in operations time instead of tasks — so the hours you save (ב) are not eaten by an unnoticed multiplier that cuts margin (א).

What changed on Zapier: AI priced by model tier

On June 15, 2026, Zapier began pricing AI by Zapier steps by model tier. The tier sets how many tasks that step uses per run. Zapier’s current model tier pricing help (updated October 1, 2026) documents:

Formula (from Zapier Help):

Tasks used per run = (1 × model rate) + (number of tool calls × model rate)

Worked examples from the same page:

• Premium (5x), no tools → 5 tasks
• Premium (5x), 2 tool calls → 15 tasks (5 + 10)
• Advanced (3x), 1 tool call → 6 tasks
• Your own AI account (1x), 4 tool calls → 5 tasks

Tasks = (1 × model rate) + (tool_calls × model rate) — worked examples from Zapier Help.

Credit: Linksh / Vesper · Visual · original. Formula/examples from Zapier Help. Not a Zapier asset.

That is how a “simple” agent-style step with two lookups becomes a double-digit task hit. Zapier also documents a per-step task limit (default 75, raisable up to 500): if a live run hits the limit, the Zap pauses and asks you to approve before continuing — a circuit breaker against runaway tool loops (model tier pricing).

Default caveat: Zapier’s June 15 announcement article (still online, updated August 12, 2026) said new steps defaulted to Advanced (3x). The October 1, 2026 tier page says new paid AI by Zapier steps default to Premium (5x). If you create steps today, check the picker — do not assume the launch-era default. Free plans preview AI at Standard and lock Advanced/Premium until upgrade (Add tools).

Legacy AI by Zapier steps created before June 15, 2026 are not auto-migrated to tools/tiers; Zapier documents separate rules (including pauses around June 30, 2026 for some legacy Standard + knowledge setups). Treat rebuilds as a chance to pick the right tier deliberately.

The other meter: n8n charges full executions

n8n’s pricing page states the opposite unit: monthly workflow executions, “regardless of complexity,” and “Pay for full executions, not for each step.” One run of a 3-step workflow and one run of a 30-step workflow can count the same as one execution on that model — the cost pressure is how often the workflow fires, not how many AI tool hops sit inside a single run.

Cloud plans on that page list Starter from €20/mo and Pro from €50/mo when billed annually (verify live pricing when you buy). A Community Edition self-hosted build is available via GitHub; you bring the server. n8n notes Cloud data hosted in Frankfurt, EU.

For agent-heavy graphs, execution billing can be cheaper if many steps would have multiplied tasks elsewhere — and more expensive if you trigger the workflow thousands of times for tiny jobs. The meter changed; the workload still decides the bill.

Make: credits, and AI that can move with tokens

Make’s Credits help (updated October 1, 2026) explains credits as the billing currency. Roughly:

• Many non-AI modules: 1 operation ≈ 1 credit (fixed).
• Third-party AI apps with your connection: Make credits for operations; you pay the AI provider for tokens.
• Make’s AI Provider: credits based on tokens (and operations), with published input/output tokens-per-credit tables by model tier.
• Custom AI provider on paid plans: Make credits on operations; provider bills tokens.

On August 25, 2026, Make updated Small/Medium/Large AI Provider rates to separate input vs output token prices, generally making input-heavy steps cheaper than the prior combined-token model (Make Help). So Make AI cost is not only “how many modules” — long prompts and big extractions move the needle.

Stay, switch, or self-host

Three meters: Zapier task multipliers (1x/3x/5x + tool calls), n8n full executions, Make credits (tokens for some AI). Decide stay, switch, or self-host.

Credit: Linksh / Vesper · Visual · original (polished from Remy · Reporter draft). Aligned to Zapier/n8n/Make Help accessed 2026-10-02. Not a vendor asset.

Stay (on Zapier) when…

• Your team already lives in Zapier, and rewriting hundreds of Zaps would cost more than a month of tasks.
• You can drop the tier: Standard for prompt-only; Advanced instead of Premium when tools are enough; BYOK at 1x for tool-heavy runs (Zapier tier table).
• You will use the 75-task pause as a feature: inspect tool-looping agents before they burn the month.
• Volume is moderate and predictability of the Zap ecosystem matters more than raw unit economics.

Switch (billing model) when…

• A single AI step routinely fans out into many tool calls and your task graph looks like a tree. Execution-based (n8n) or credit + BYO token (Make) may match the workload better.
• You are designing new agent workflows, not migrating a decade of Zaps — greenfield is when model shopping is cheapest.
• You need “one run ≈ one billable unit” that finance can forecast without per-tool task math.

Self-host when…

• You choose n8n Community (or similar) because data location / VPC / custom nodes matter, or execution volume would dominate Cloud invoices.
• You have someone who can own updates, backups, secrets, and uptime. Self-host is not free — it moves cost from SaaS tasks to engineering time (n8n pricing Community vs Cloud framing).
• Compliance wants the runtime on infrastructure you control; Cloud Frankfurt (n8n) or vendor regions may or may not be enough — that is a policy call, not a slogan.

A practical cost-check before you ship an “AI” workflow

1. Count tool calls in a realistic run, not the happy path. Two searches + one write = three multipliers on Zapier.
2. Open the model picker. If it says Premium and you only need classification without tools, switch to Standard (1x) or Advanced if you need one tool.
3. Try BYOK on Zapier for tool-heavy steps if you already pay OpenAI/Anthropic — Help calls it the most cost-effective option for that pattern.
4. Compare meters on the same scenario: “50 runs/day, ~8 steps, 2 AI tool calls each.” Spreadsheet tasks×multiplier vs executions vs credits.
5. Set the Zapier per-step task cap intentionally if the agent can loop.
6. On Make, decide Make AI Provider vs your own key before volume — token tables and provider invoices stack differently (Credits).
7. Re-read Help after pricing updates. Defaults and token tables moved in 2026; screenshots from June can mis-teach October.

Owners and freelance automation builders should price client retainers on expected tasks/executions/credits, not on “number of Zaps.” A Premium default you never noticed is a silent raise for the vendor and a silent cut for your margin — automation that saves hours only helps take-home if the meter does not eat what you freed.

This is product billing hygiene — not investment, tax, or legal advice. Plan names and list prices change; follow the Help links above when you renew.

Bottom line

Multipliers punish chatty agents on task-priced platforms; execution pricing punishes chatty triggers; credits punish token-heavy prompts. Stay if you can tune tier and BYOK. Switch if the meter mismatches the workflow shape. Self-host if control and volume beat SaaS convenience — and budget the humans who keep the lights on.