Is 1 operation still equal to 1 credit on Make.com?

Yes, for most standard modules, 1 operation still equals 1 credit. However, some AI-powered modules may consume additional credits depending on complexity.

Will I pay more under the new Make.com credit system?

Not necessarily. If you use standard modules, your costs remain the same. AI modules using Make’s internal provider may cost more credits per run.

Can I still use my own OpenAI or Claude key with Make?

Yes. When using your own AI key, each run still costs just 1 credit in Make.com, while you pay tokens separately through your provider.

How can I track or reduce my credit usage?

You can monitor usage in Make’s dashboard or set up logging to Airtable. Use filters and avoid large token loads in AI calls to reduce consumption.

How can Scalevise help with this?

Scalevise helps businesses turn complex digital challenges into scalable solutions. Whether you're facing compliance, automation, integration, or innovation hurdles — our team delivers custom strategies and implementations that work. Contact us today at contact@scalevise.com or call +31-6-27178770 to find out how we can help you move forward.

Make.com’s New Credit System Explained: Are You Paying More?

Name: Make.com Credit System
Brand: Make
Rating: 4 (1 reviews)

3 min read

Make.com Credit Costs Explained

On August 27, 2025, Make.com officially switched its billing system from operations to credits. While this may seem like a simple renaming at first, the change has deeper implications especially for teams using AI modules or working at scale.

Let’s unpack what this shift means, whether you’ll end up paying more, and how to adapt your workflows for maximum cost-efficiency.

From Operations to Credits: What’s New?

What Stayed the Same:

1 operation = 1 credit for standard modules
Your monthly plan and pricing remain unchanged
Existing operations were converted 1:1 into credits

So if you previously had a 10,000 operations/month plan, you now have 10,000 credits.

⚠ What Changed:

Credits are now the billing unit, not operations
AI modules (especially those powered by Make’s built-in AI provider) now consume more than 1 credit depending on complexity, token count, or file size

Understanding Credit Consumption

Not all modules are equal anymore. Here’s the breakdown:

Standard Modules

Still cost 1 credit per operation
Includes tools like Airtable, Gmail, Webhooks, HTTP, etc.

AI Modules via Make’s Own Provider

These now consume extra credits, depending on:

Token usage (e.g., GPT-style modules)
File size (e.g., PDF parsing or document extraction)
Image count or page count

Example:

A simple AI email generation might use:

1 credit (operation)
0.1 credit (for 145 tokens)
➡ Total: ~1.1 credits

A long document summary (e.g., 2,000+ tokens) could use:

1 credit (operation)
1.5 credits (AI processing)
➡ Total: ~2.5 credits

Want to optimize AI usage across your workflows? Schedule a call with Scalevise to evaluate your setup.

Third-Party AI (OpenAI, Claude, etc.)

Still just 1 credit per operation
You pay token usage directly to the AI provider
No surprise consumption within Make

How to Check Your Credit Usage

Make.com now includes a detailed breakdown of credit consumption:

Per scenario
Per module
Per individual run

You can also log credit usage into Airtable or export reports for billing transparency.

Should You Be Concerned?

Let’s be direct:
If you don’t use AI modules, this change will not affect your cost.

If you do use AI modules via Make’s internal tools, your credit usage can spike, depending on:

Length of prompts
Number of tokens or file pages
Whether your AI module is set to “Large” tier (more credits per token)

Best Practices to Control Costs

Audit your AI usage
Start with your most frequent scenarios. Are they using Make’s internal AI or your own OpenAI key?
Set limits on token size or file size
Add filters and conditional logic to skip oversized files.
Switch to external AI keys
Using your own OpenAI or Claude keys means stable 1 credit per call.
Log usage in real time
Build a credit monitoring dashboard using Make + Airtable.

Our Take at Scalevise

For most businesses, this is not a price hike yet.
But if you’re scaling up automation or integrating LLMs into your stack, it will affect your usage strategy.

At Scalevise, we help companies optimize Make.com workflows for cost, performance, and growth. We can:

Rebuild heavy scenarios into efficient chains
Replace Make AI modules with direct API calls
Add logging and alerting to prevent runaway consumption

Final Thoughts

The new credit model gives Make more flexibility to price complex actions fairly. But as with any billing change, the onus is on users to stay informed.

If you’re unsure whether your team is using credits wisely or if you're planning to scale your automation stack reach out.

👉 Let’s analyze your usage together

Frequently Asked Questions

Is 1 operation still 1 credit?
Yes, for standard modules. But AI modules may consume more than 1 credit depending on the action.

Does this mean I’ll pay more per month?
Not necessarily. But if you're using AI modules from Make’s internal system, costs can increase.

Can I still use OpenAI or Claude via API?
Yes. You’ll still pay 1 credit per operation in Make, and handle AI costs separately with your provider.

Can Scalevise help reduce credit usage?
Absolutely. We specialize in optimizing Make workflows. Contact us for a free assessment.