Usage and billing guide

Make.com credits too expensive? Estimate usage first

If Make ran out of credits, start by tracing actual consumption to scenarios and modules before buying more capacity or rebuilding. Make changed the billing unit from operations to credits, while stating that its plans and prices were unchanged at conversion. AI features can use more credits, so estimate from measured usage, expected scenario runs, and realistic peaks—not from a guessed average across every workflow.

Make's operations-to-credits conversion

Make states its plans and prices were unchanged at conversion on 27 August 2025. One operation equaled one credit. AI features can use more credits than this one-to-one conversion, so check the consumption of the modules in your scenarios. Checked October 2026, confirm on the vendor's pricing page.

The billing-unit conversion alone does not mean an account's plan price changed. Use your own account history and current billing documentation to estimate consumption. Checked October 2026, confirm on the vendor's pricing page.

Why credits can run out sooner than expected

A scenario may be scheduled more often than its task requires. Polling can wake it when nothing has changed, while event bursts, retries, and parallel copies raise total consumption. AI modules can use credits at different rates from a simple operation-to-credit conversion, so a flat rate for every step can mislead.

When a balance seems to drop unexpectedly, examine several representative runs rather than only the last one. Compare the scenario start count with the number of successful business outcomes. Review failure loops, incomplete runs, duplicated schedules, and test scenarios. Confirm the current Make definitions for any module whose credit rate matters; billing terms and module behavior can change.

Estimate usage with your own evidence

1. Choose a representative period that includes normal volume and at least one busier interval.
2. For each scenario, record starts, completed work, errors, retries, and credits consumed from the available history.
3. Calculate a practical observed average per run for each scenario. Do not assume the average applies to a different module or AI operation.
4. Multiply by the number of expected future runs. Add a separately stated allowance for known peaks and failures rather than hiding uncertainty in a single estimate.
5. Test ways to reduce unnecessary work, then compare the new measured rate with the old one and re-check the plan terms.

This estimate does not replace Make's own current credit display or pricing rules. Keep a record of assumptions, especially when a scenario uses AI. If credits are still unpredictable after tuning, compare a billing model that better matches how you forecast your workload.

How iii3xnz counts executions

iii3xnz publishes plan limits in workflow executions. Its backend stores an execution record for each workflow run and counts those records within each plan's daily or monthly window; steps are stored in the run log rather than billed as separate execution records. In the frontend contract and backend limits, Free includes 250 executions per day and 3 workflows; Starter includes 20,000 executions per month for $15 and 25 workflows; Pro includes 150,000 per month for $99 and 9,999 workflows. All plans include the same 46 node types; the registry is not a count of third-party integrations.

That model can make a rough volume estimate easier when you already know how many whole workflows start. It does not guarantee that a particular automation is supported or that your total costs will be lower. Review the available node definitions and plan limits, then test the behavior you depend on. The published windows differ: the Free allowance is daily while Starter and Pro allowances are monthly.

Where Make is better

Make may be the right choice if its scenario builder, modules, existing account connections, or current billing terms fit your work. If your team already has stable scenarios, rebuilding them has a real testing and maintenance cost. Compare the modules you need and measure actual credit use before moving. The point is to understand the billing unit and your consumption, not to assume that one platform is always less expensive.

Frequently asked questions

What changed in Make billing?

Make states its plans and prices were unchanged at conversion on 27 August 2025. One operation equaled one credit, and AI features can use more credits. Check Make's current pricing and billing documentation.

Why did Make run out of credits?

Frequent polling, high event volume, retries, and modules with different credit rates can consume the available balance faster than expected. Measure actual scenario usage and inspect the current credit rules rather than assuming every module costs the same.

How can I estimate Make credit use?

Use observed credits per representative run, multiply by expected runs for the billing period, and include realistic peaks and retries. Validate the estimate against Make's usage history and current pricing details.

How does iii3xnz count executions?

The backend records an execution for a workflow run and counts execution records against the plan window. Its published limits are based on workflow executions, not an operation-to-credit conversion. Review the current plan limits before switching.