# Make.com Pricing Explained: Credits, Operations and Plan Limits

> Understand how Make bills in credits, which plan limits besides credits can affect you, how AI modules change the math, and how to avoid running out mid-month.

Source: https://www.epifive.com/blog/make-com-pricing-credits-operations-explained · Published 2026-10-31 · EpiFive

## Key takeaways

- Make bills in credits, and for non-AI apps one operation equals one credit.
- Credits are not the only limit, because data transfer, storage and webhook queue size also scale with the credits on your plan.
- AI modules can use credits based on tokens, and the cost depends on whether you use Make's AI provider or your own connection.
- Check Org > My Plan > Credit usage to find which scenarios burn credits before you hit the limit.
- When credits run out, scenarios stop until you add credits, so decide in advance between extra credits, auto-purchase or a bigger plan.

Make bills in credits, and for non-AI apps one operation equals one credit. A plan gives you a monthly pool of credits, and when the pool is empty your scenarios stop until you add more. Credits are not the only limit: data transfer, storage and webhook queue size scale with the credits you license, and AI modules can use credits based on tokens rather than a flat per-operation rate.

This guide is for people choosing or upgrading a Make plan, and for anyone whose scenarios stopped unexpectedly. By the end you will know how credits relate to operations, what the extra limits are, how AI modules change the cost, where to monitor usage, and how to plan so you do not run out. For a worked method that estimates credit use from a scenario's schedule and bundles, read [Make.com operations and pricing: estimate your monthly credit use](https://www.epifive.com/blog/make-com-operations-pricing-explained). This article covers the plan side of the same question. If you are comparing tools, see [n8n vs Make vs Zapier](https://www.epifive.com/blog/n8n-vs-make-vs-zapier).

Pricing details were checked on 31 October 2026 on Make's pricing page and Help Center. The pricing page's text showed the Free plan's credits but not the paid plans' prices or credit amounts, so this article does not quote them. Open the pricing page for the current figures in your currency.

## Who this is for and what you will have at the end

You build automations in Make for yourself or a small business. After reading you will have a way to size a plan, a short list of limits to check beyond credits, and a monitoring routine that warns you before a scenario stops.

## Prerequisites

- A Make account with at least one scenario that has run, so there is usage to look at.
- Access to the organization view in Make (the Org item in the left sidebar).

## Credits and operations

Make's Help Center explains that credits are the billing unit and operations show the outcome of your activity. It states that "credits and operations are separate terms because they serve different purposes," and that by default 1 operation equals 1 credit for non-AI apps. Only features triggered by scenario runs, plus the AI agent's chat, consume credits.

Usage can be fixed or dynamic:

- **Fixed:** most apps use a set rate per run that does not change with input or data size.
- **Dynamic:** usage varies with tokens, file size, pages processed or run time. Tokens are the most common factor.

An example from the Help Center: Google Drive Upload a File uses 1 credit per upload regardless of file size, while some Make AI Content Extractor modules use more than the default, with examples of 2 or 10 credits per operation. The page does not list every module's cost, and it points to a "Credits by module type" section for examples, so check the module's documentation for anything you rely on.

## Limits that scale with your credits

Make's pricing page lists allowances that grow with the credits on your plan. Per 10,000 credits licensed per month:

| Limit | Allowance per 10,000 credits |
|---|---|
| Data transfer | 5 GB |
| Data storage | 10 MB |
| Incomplete executions storage | 10 MB (2 GB maximum) |
| Webhook queue size | 667 (10,000 maximum) |

So a plan with more credits also gets more transfer and queue room. If your scenarios move large files, data transfer can bind before credits do. The Credit usage table described below shows data transferred per run, which helps you check this.

The page also says companies with under 20 employees may qualify for 50% off a Business plan under a start-up program. Eligibility rules were not shown, so confirm on Make's site before you plan around it.

Other limits depend on your plan and are documented per plan, for example the minimum scheduling interval. Make's scheduling page says the minimum interval "depends on your plan" without listing values, so check the plan cards. By default a scenario runs every 15 minutes.

### Instant triggers and rate limits

For scenarios with instant triggers, the default scenario rate limit is 100 runs per minute, and you can set a lower maximum. Requests above the limit are queued. For scenarios with a Webhook response module, callers receive an HTTP 429 error when the limit is exceeded and must retry later. If you call these webhooks from your own code, handle 429 with backoff as described in [handling LLM API rate limits in Python](https://www.epifive.com/blog/llm-api-rate-limits-retry-backoff-python), which applies the same pattern.

## How AI modules affect credits

Make's credits page describes three ways AI modules are billed, depending on the connection:

- **Make's AI Provider (all plans):** credits are based on tokens and operations.
- **Custom AI provider connection (paid plans):** you pay Make credits based on operations and pay your provider directly for tokens.
- **Automatic AI provider connection (all plans):** credits are based on tokens, operations and other usage factors. This applies to Make AI Web Search, Make AI Content Extractor and certain Simple Text Prompt modules.

For token-based costs the page gives a rule of thumb that English text averages about 4 characters per token. It lists the Large tier under Make's AI Provider (GPT-5 mini) at 3,616 input tokens per credit and 452 output tokens per credit. These figures can change, so read the current page before budgeting.

A worked example using those figures: a prompt of 3,616 input tokens that returns 452 output tokens would cost about 1 credit for input plus 1 credit for output, so about 2 credits, plus the operation credits of the surrounding modules. Treat this as an estimate to verify against Credit usage after a few runs.

The practical lesson is that a custom connection moves token cost to your AI provider's invoice, while Make's own provider keeps everything in credits. Pick based on which bill you want to watch.

## Step-by-step: size a plan

1. **Measure real usage.** Run each scenario with typical data and open its execution history.
2. **Read Credit usage.** In the left sidebar choose Org, then under My Plan select Credit usage. The table lists the scenario or AI agent, credits used per run, data transferred per run and a timestamp. Select a run's name to see detailed credit use in the execution log. This is available on all plans.
3. **Multiply by frequency.** Credits per run times runs per month gives the scenario's monthly credits. Add all scenarios.
4. **Add headroom.** Spikes happen when a trigger returns many bundles at once. Leave room rather than planning for 100% of the pool.
5. **Check the other limits.** Compare data transferred and webhook volume with the allowances in the table above.
6. **Compare plans on the pricing page.** Look at the credits, scheduling interval and features on each plan card.

## What happens when credits run out

Make's pricing FAQ says your scenarios will not continue to run until credits are added again. Incoming webhooks are queued up to your queue limit and processed after credits are added. Polling scenarios pick up records from their last successful run.

Your options, as the page lists them:

- Upgrade the plan.
- Buy extra credits, in bundles of 1,000 or 10,000 at the fixed price in your subscription.
- Turn on auto-purchase of 10,000 credits, available on Core, Pro and Teams plans.

Extra credits expire after one month on monthly subscriptions, or at the end of the year on annual Pro and Teams subscriptions. If you only occasionally exceed your pool, extra credits are a bridge. If it happens every month, upgrade.

Auto-purchase avoids interruptions but spends money without you reviewing it, so decide on it deliberately.

## Notifications and team limits

Team credit limits and the 75%, 90% and 100% email notifications are for Enterprise customers. Per Make's documentation, owners and admins set a credit limit per team, a team's scenarios pause when it uses its allocation, and lowering a limit below current usage pauses the team immediately. If you are not on Enterprise, build your own check: review the Credit usage table weekly, and place a notification step in your most important scenarios' error handling so a stoppage is visible.

## Troubleshooting

### Scenarios stopped with no error in the scenario itself

Check whether credits are exhausted. Open the Dashboard or the Subscription page for credits left and the reset date, then add credits or wait for the reset.

### Usage is much higher than expected

Open Credit usage and sort mentally by scenario. Look for scenarios whose runs use many credits each, such as ones with a trigger returning many bundles or AI modules. Reduce frequency, filter early or aggregate bundles, as described in the [operations guide](https://www.epifive.com/blog/make-com-operations-pricing-explained).

### A webhook returns HTTP 429

You exceeded the scenario's rate limit (default 100 runs per minute). Lower the caller's rate or retry with backoff.

### Data transfer is the limiting factor

Check data transferred per run in Credit usage. If large files are the cause, process fewer or smaller files per run, or move to a plan with more credits since transfer scales with them.

## Checklist

- Read credits per run from Org > My Plan > Credit usage.
- Total monthly credits and add headroom.
- Check data transfer, storage and webhook queue allowances.
- Decide how AI modules are billed: Make's provider or your own connection.
- Choose upgrade, extra credits or auto-purchase before you run out.
- Review usage weekly.

## References

- [Make pricing](https://www.make.com/en/pricing)
- [Make Help Center: Credits](https://help.make.com/credits)
- [Make Help Center: Credit usage history](https://help.make.com/introducing-credit-usage-history)
- [Make Help Center: Credits per team management](https://help.make.com/credits-per-team-management)
- [Make Help Center: Schedule a scenario](https://help.make.com/schedule-a-scenario)

## Frequently asked questions

### Does Make charge per operation or per credit?

Make bills in credits. For non-AI apps one operation equals one credit, so the numbers match. Modules with dynamic usage, such as AI modules, can use more or fewer credits than operations depending on tokens, file size, pages or run time.

### How many credits does the Make Free plan include?

Make's pricing page says the Free plan has 1000 credits per month. Prices and credit amounts for the paid plans were not shown in the text of the pricing page when checked, so look at the plan cards on the page for current figures.

### What happens when I run out of credits in Make?

Make states that your scenarios will not continue to run until credits are added. Incoming webhooks are queued up to your queue limit and processed after credits are added, and polling scenarios pick up records from their last successful run.

### Where can I see how many credits each scenario used?

In the left sidebar, open Org, then under My Plan select Credit usage. It lists each scenario or AI agent run with credits used, data transferred and a timestamp, and it is available on all plans.