What do you actually pay for with Make.com?
Since August 2025 Make has charged in credits. An operation is an action a module performs. A credit is what you pay for it with. For ordinary modules, one operation is one credit, however large the data. If you come across older articles that talk about operations, you can usually read those numbers one to one.
According to Make's documentation (checked on 2 November 2026), usage works like this:
- Triggers: 1 credit per run, even when nothing new is found.
- Ordinary modules: 1 credit per operation, and they run once for every bundle that comes in. A bundle is one set of data, for example one order.
- Iterators and aggregators: 1 credit each time they split or combine.
- Routers, filters and error handlers: 0 credits.
- The Code app: 2 credits per second of execution time.
- AI: depends on the setup. Through Make's AI provider you pay 1 credit per operation plus credits for token usage. With your own connection to an AI vendor you pay 1 credit per operation and pay for the tokens directly to that vendor.
The most important rule is in the second bullet. Bundles multiply. If your trigger fetches 200 orders and you do five things per order, that single run costs 1,001 credits.
Which plan suits which situation?
The amounts change regularly, so always check Make's pricing page before you decide. The position on 2 November 2026:
- Free: 1,000 credits per month, two active scenarios and at least 15 minutes between runs. Good for trying it out, too tight to run a business process on.
- Core: from 10,000 credits, unlimited active scenarios and runs up to every minute. The logical starting point for most SMEs.
- Pro: adds, among other things, priority execution, custom variables and full-text log search. Useful when you need to be able to trace several scenarios properly.
- Teams: adds multiple users with roles. Only relevant when several people build or manage scenarios.
- Enterprise: custom, on request.
About the prices: in its own explanation of extra credits, Make uses an example of $9 for 10,000 credits, so $0.0009 per credit. Independent overviews from 2026 mention roughly $9 for Core, $16 for Pro and $29 for Teams on annual billing, but those amounts vary by source and monthly billing costs more. Treat them as an order of magnitude, not a quote.
How do you calculate your usage upfront?
A fictional example to make it concrete. A wholesaler with fifteen employees wants to automate three processes. Here is the calculation, in four steps.
- Write down the steps per scenario. Count only modules that cost credits.
- Estimate the monthly volume. How many requests, orders or invoices come through?
- Count the triggers separately. How often does the scenario run, even when there is nothing to do?
- Add it all up and add a 30% margin. For test runs, repeated runs and busy months.
Scenario 1: a request through the website. A form sends a webhook. Make looks up the customer in the CRM, creates or updates the contact and prepares a task. That is 1 + 3 = 4 credits per request. At 200 requests per month: 800 credits.
Scenario 2: reminders for overdue invoices. Every working day at 8:00 a trigger looks up the overdue invoices, 15 on average. For each invoice an email goes out and a note is added to the CRM. That is 1 + (15 × 2) = 31 credits per run. Over 21 working days: 651 credits.
Scenario 3: orders from the webshop. A trigger checks every fifteen minutes for new orders. That is 96 times a day, so 2,880 credits per month just for checking. On top of that, 300 orders with three actions each: 900 credits. Together 3,780 credits.
The total is 5,231 credits, about 6,800 with a 30% margin. That fits comfortably in a 10,000-credit plan. The free plan is out: too few credits, and you can only have two active scenarios.
Now compare that with the cost of the manual work. If retyping one request takes five minutes, 200 requests take more than 16 hours a month. The licence is rarely the cost that decides the matter.
How do you keep your credit usage low?
Most of scenario 3 is checking when there is nothing to do. That is exactly where the savings are.
Use a webhook where you can. If the webshop sends a signal itself for each new order, the scenario only runs when there is actually something to do. That costs 4 credits per order, so 1,200 credits instead of 3,780. The total drops to 2,651 credits. Not every system can send webhooks. How to make that choice per system is covered in building a Make.com integration.
Choose an interval that fits the question. The interval of a scheduled trigger sets your fixed usage:
- every fifteen minutes: 2,880 credits per month;
- every 5 minutes: 8,640 credits per month;
- every minute: 43,200 credits per month.
So one scenario that checks every minute uses more than a 10,000-credit plan contains, before anything has been done. Does an overview really have to be current every minute, or is three times a day fine too? That is often the cheapest question you can ask.
Filter as early as possible. Filters cost nothing, the modules behind them do. Put a filter directly after the trigger, so records you do not need no longer cost any steps.
Fetch what you need in one go. Fetching a list and then requesting the details per row costs an extra credit per row. If the first module already returns the fields, you can skip that step.
Calculate AI separately. AI steps often cost more than 1 credit and usage varies per email or document. In one of Make's examples, the same AI step on three emails costs 1.19, 1.43 and 2.56 credits. Test with real examples before you estimate usage. What you should and should not leave to an agent is covered in Agentic AI for SMEs.
What happens when your credits run out?
This is worth thinking about upfront, because your scenarios stop. According to Make's FAQ (checked on 2 November 2026), it works like this:
- Scenarios only run again once credits have been added.
- Incoming webhooks are queued, as long as there is room for them.
- Scenarios with a scheduled trigger then fetch whatever has been added since the last successful run.
You have three options: move to a larger credit tier or higher plan, buy extra credits or turn on automatic purchasing. Extra credits cost 25% more than the credits in your plan. In the example of $9 for 10,000 credits, an extra bundle of 10,000 credits therefore costs $11.25. For a one-off peak that is fine. If you top up every month, a larger credit tier is cheaper.
Unused credits do not simply carry over: they expire at the end of the term. So an oversized plan "just to be safe" simply costs you money. Keep an eye on your usage and check after the first month whether your estimate was right. How to stop a scenario from quietly failing is covered in Make.com error handling.
When does Make.com become too expensive?
Make charges per step per record. That is good value for individual events and gets expensive when you process large lists. Suppose you want to update 5,000 records in two steps every night for a report. That is 10,000 credits per night, or around 300,000 credits per month. That is currently exactly the upper limit of the Core plan.
There are two logical alternatives:
- A platform that charges per run. With many steps per run n8n can be cheaper, although with self-hosting you pay that back in maintenance. The trade-off is covered in Make vs n8n.
- A data pipeline or data foundation. If the goal is reporting, that data should not go through a workflow tool record by record. A central data foundation fetches it in bulk and has it ready. Make stays useful for the actions around it, such as creating a task or sending an alert.
Need help calculating your Make.com automation?
Want to know what your processes will use in Make, or is your credit usage rising faster than you expected? We are happy to look at your scenarios and systems and work out which setup fits. See what we do in workflow automation, which integrations we often build, or read how we work.
