Make.com's per-step credit billing can sharply raise costs for complex automations

A May 12, 2026 guide explains that Make.com charges one credit per module execution, making costs predictable but able to escalate quickly for multi — step or high-frequency workflows.

A May 12, 2026 guide lays out how Make.com bills for automation: every trigger, filter, action or module execution consumes at least one credit. That per-step, per-execution model makes per-run costs measurable, but it can also produce steep monthly bills for teams running complex or frequent scenarios — a practical risk for operations that depend on reliable, always — on automations.

Make.com is a visual automation platform where users build workflows called “scenarios” by placing modules on a canvas. Scenarios can connect to more than 3,000 apps, including Gmail, Slack and Google Sheets, and support routers, filters, custom logic and code. The platform also supports code execution through the Make Code app (JavaScript or Python) and includes AI features — AI agents, an AI toolkit and integrations with over 350 AI apps-all of which can be embedded into scenarios.

The guide explains billing mechanics with concrete examples: each module execution costs at least one credit, so a five-step scenario run 100 times in a month uses 500 credits and a 20 — step scenario run 500 times consumes 10,000 credits. Costs vary by module mix because some modules charge extra: Make Code is billed at two credits per second of execution time, and certain AI actions draw additional credits, so a single scenario’s per-run cost depends on both step count and which modules are used.

Make offers a free tier that supplies 1,000 credits per month for light use and testing. Paid plans start at $12 per month when billed annually for a Core plan that includes 10,000 credits. Higher tiers raise monthly credit allowances and add features such as priority execution, team roles and enterprise security. Annual billing typically reduces cost by about 15% or more versus monthly payments. If a workspace exhausts its monthly credits, scenarios stop running until the next billing cycle or until the account is upgraded or extra credits are purchased.

For builders and teams the guide frames the trade — offs clearly: credit accounting provides transparency — you can count modules and estimate runs-but complex workflows and high-frequency automations can quickly deplete allowances. The guide recommends practical steps: audit step counts and execution frequency, check module — specific credit rules (notably Make Code and AI modules), and consider annual billing or higher tiers where priority execution, security controls and reliability are critical.