Make.com Is Moving to Credits: The 2025 Pricing Shift

Updated August 13, 2025

TL;DR

On August 27, 2025, Make.com will switch from counting operations to using credits as its billing unit. Most actions still cost 1 credit, but advanced features—mostly AI modules—may use more, either at a fixed rate or based on actual usage (e.g., tokens, file size, or pages). Your plan, price, and limits won’t change, and your operations balance converts to credits at a 1:1 rate automatically. “Operations” will still appear in scenario logs for data tracking—not billing.

What’s Changing—and What’s Not

  • New billing unit: Credits replace operations for billing starting August 27, 2025.
  • Automatic conversion: Existing operation balances convert to credits at 1 Operation = 1 Credit; no action required.
  • Your plan & price: Stay the same. Manual and automatic purchases of extra credits work as before.
  • Operations don’t disappear: They remain visible as a data/activity metric in run history—not a billing meter.
  • Docs: Make’s details: help.make.com/credits.

Most Actions = 1 Credit

For common modules and standard API calls, expect a straightforward 1 action = 1 credit model—keeping day-to-day automations predictable.

Advanced / AI Features May Cost More

Some features—especially AI-powered modules—consume more credits or vary by usage (e.g., tokens, pages, file size, runtime). Check module docs when estimating costs.

Credits vs. Operations (Why You’ll See Both)

Purpose
Credits: Billing unit for spend.
Operations: Activity/data indicator in run history.
Where You See It
Credits: Usage dashboards, subscription panels.
Operations: Run bubbles/history, module logs.
How It’s Counted
Credits: Per action; some features consume more.
Operations: Steps executed—useful for optimization.
Conversion
Credits: Replace operations for billing.
Operations: Still visible for analysis; not a billing meter.

What Happens on August 27, 2025

  • Automatic 1:1 conversion: Your operations balance becomes credits. No downtime or migration clicks.
  • Same plan, same price: Your subscription tier stays intact; only the billing meter changes.
  • History continuity: Scenario history continues to show operations alongside credits for clarity.

How to Track & Manage Credit Usage

  • Subscription/Usage panels: Monitor total credits used and remaining in your current cycle.
  • Scenario history: Inspect credits per run and at the module level to spot outliers.
  • Alerts & top-ups: Set alerts or enable auto-purchases so busy periods don’t stall automations.

Optimization Playbook (Practical Tips)

  • Filter early: Use routers/filters at the top of scenarios to prevent unnecessary downstream steps.
  • Batch where possible: Group writes/updates to reduce per-item actions when APIs allow it.
  • Consolidate transforms: Combine adjacent text/array functions to cut superfluous actions.
  • Externalize heavy AI: For large prompts or long documents, call your AI provider directly via HTTP and re-ingest summarized results.
  • Watch big inputs: Large files or multi-page documents can trigger higher usage in advanced modules—trim inputs before processing.
  • Instrument & iterate: Review high-credit runs weekly; refactor hot spots.

FAQ

On August 27, 2025, Make.com replaces operations with credits as the billing unit. No action is required—your existing operations balance converts to credits automatically at a 1:1 rate (1 Operation = 1 Credit).
No. Your plan and price stay the same. Manual and automatic purchases of extra credits work the same way they did for operations.
Most actions consume 1 credit per action. Advanced features—especially AI—may consume more, either at a fixed cost or based on usage (for example, tokens, file size, or number of pages).
Operations will no longer be a billing unit, but they remain visible in scenario execution as a data or activity metric. You can still use operations counts in history to analyze and optimize workflows.
When appropriate, call your AI provider directly via an HTTP/API module (e.g., OpenAI or Anthropic) and feed results back into Make. You will still spend credits for the HTTP call and subsequent steps, but the AI processing is billed by your provider rather than through Make’s AI modules, which can help control credits for heavy AI workloads.
By Published On: August 13, 2025

Ready to Start Automating?

Let’s talk about what’s slowing you down—and how to fix it together.

Share This Story, Choose Your Platform!