Make.com Pricing: Plans, Credits & AI Costs

Buying path

Start in the free workspace and build a representative scenario before choosing a paid tier. The useful baseline is not the number of scenarios you can imagine but the module activity, polling frequency, bundles, AI calls, and retries produced by a normal month. That test reveals whether the entry paid workspace is enough and gives you a defensible credit budget.

The default paid path is the lowest self-serve tier that removes the free workspace's scheduling and active-scenario constraints while opening the Make API and custom AI-provider connections. Higher tiers should solve a demonstrated performance, collaboration, governance, or credit-allocation need rather than serve as insurance against an unmeasured workflow.

Upgrade triggers

Move beyond free access when production schedules need to run more frequently, more than a small set of scenarios must remain active, or a workflow needs programmatic platform control. Credit volume is a separate trigger: count every module that processes bundles and model the busiest periods, because one scenario run can create many billable actions.

Upgrade again when execution priority, deeper log search, shared templates, team roles, or organizational administration becomes part of the operating requirement. If extra-credit purchases become routine, compare a larger included allowance or higher tier before accepting repeated surcharges. The cheapest plan label is not the cheapest operating state when workflows regularly stop or depend on manual top-ups.

API and team boundaries

The Make API is a control surface included with paid workspaces, not a separately metered developer product with its own public plan. Its rate limit rises by tier, while the same organization's Make credits continue to fund scenarios. A team workspace adds collaboration controls but does not create an independent pool for every member, so ownership and usage monitoring should be agreed before multiple builders deploy automations.

AI spending has another boundary. Make's AI Provider converts model operations and tokens into Make credits, while a custom provider connection on a paid plan uses Make credits for operations and sends token charges to the provider account. Neither route should be budgeted as though the workspace allowance and external model bill were one number. Enterprise remains a sales-assisted agreement for custom capacity, governance, security, connectivity, support, and procurement.

Final pricing check

Before paying, verify the selected credit tier, billing cycle, annual commitment, regional currency, taxes, and credit-expiry rules. Annual billing does not allocate credits identically across every self-serve plan, and extra credits have their own surcharge and validity window. Check the actual scenario estimate against both the included credits and the surrounding data-transfer, storage, queue, file-size, and execution limits.

Finally, confirm who owns connections and provider keys, which users may create or activate scenarios, the API rate limit, and whether any beta AI feature is acceptable for the workflow's risk level. Enterprise buyers should put SSO, audit, data region, on-premises access, uptime, support, overage protection, and renewal terms into the reviewed order form rather than infer them from the public matrix.