Make at $12–38/mo Sets New Automation Pricing Standard

Make's credit-based pricing — Core at $12/mo, Pro at $21/mo, Teams at $38/mo on annual billing — establishes a model that charges more for AI features without touching base pricing. Our verdict on Make stays conditional: it's the strongest Zapier alternative on price-to-flexibility ratio, but the credit model adds a cost variable you need to test before scaling.

How Make's credit pricing works

Make's pricing model has settled into its current form with three key elements:

Current pricing (annual billing, 10,000 credits/mo):

The Free plan remains at $0 with 1,000 credits/mo; Enterprise is custom-priced. Monthly billing costs roughly 15–18% more than annual (Make Pricing(opens in new tab), 2026).

Credit-based billing replaced per-operation. Since August 27, 2025, Make bills by credit consumption instead of per-operation. Most standard actions consume 1 credit, but advanced AI features — including AI Agents (now in beta), MCP server support, and the AI Toolkit — may consume more. Make's Help Center states: "Effective August 27th, 2025, we're replacing operations with credits as our billing unit" (Make Help Center(opens in new tab), 2026). This gives Make pricing flexibility as it layers AI into the platform.

Integration library passes 3,000. The 3,000+ apps milestone is significant but still trails Zapier's 9,000+ (Make Integrations(opens in new tab), 2026) (Zapier Integrations(opens in new tab), 2026).

Why it matters

Make's credit transition is the story — it lets the platform charge more for compute-intensive AI features without touching base pricing. That's a smart hedge as AI Agents move from beta to production.

At $12–38/mo for 10,000 credits, Make still undercuts Zapier's comparable tiers. But if your workflows lean on AI features, track credit consumption carefully — the gap between 1-credit actions and multi-credit AI operations compounds fast at scale.

The 3,000+ integrations milestone is worth noting but isn't the headline. Make had enough integrations for most use cases already. The real bottleneck has always been data transformation depth and complex branching — not raw connector count.

What changes for you

• Existing annual-plan users: Your price stays locked until renewal. No immediate action needed.
• New subscribers: Core at $12/mo, Pro at $21/mo, Teams at $38/mo annual. Monthly billing costs more.
• AI feature users on Make: Test your real workflows against credit consumption before scaling. A workflow that cost 100 operations could cost 150+ credits if it uses AI nodes.
• Evaluating automation tools: Make still wins on price-to-flexibility for Zapier migrants. n8n's per-execution model is cheaper for complex multi-step automations. Zapier's 9,000+ integrations still dominate if you need obscure connectors.

FAQ

When did the credit-based billing switch take effect? The switch from operations to credit-based billing took effect August 27, 2025. Existing annual-plan users at the time kept their legacy pricing until renewal.

Is 1 credit the same as 1 operation? For most standard actions, yes. But Make reserves the right to charge more credits for AI features — which is the entire point of the switch. AI Agents, MCP server calls, and AI Toolkit operations may consume multiple credits. Monitor credit burn once these features move past beta.

Should I switch to Zapier or n8n? It depends on your workload. If you rely on obscure integrations, Zapier's 9,000+ catalog is unmatched. If you self-host or run complex multi-step automations, n8n's per-execution pricing is cheaper. If you want the best visual builder with lower per-action cost than Zapier and don't mind tracking credit consumption, Make is still our conditional pick.