Make review pricing, plans & verdict

What Make is and how it works

Make is a no-code automation platform owned by Celonis. Its visual canvas is useful when a process has branches rather than one straight line. A trigger watches an app or webhook, then modules transform the data and send it elsewhere. Routers choose a path, iterators work through items, data stores keep values and error-handler modules deal with failures. Routing leads by type or handling orders differently by value are examples of the work that structure can describe.

The platform also includes AI features on every plan, including Free: Make AI Agents (beta), AI Toolkit, Content Extractor, AI Web Search (beta) and an MCP server. The server lets Claude, ChatGPT or Gemini run scenarios. Maia is the built-in assistant for building and debugging a scenario from a plain-language description on the canvas. Being able to see the generated logic is helpful, but it still needs checking before it operates on live records.

Most module actions use one credit. Reading a new row and posting two messages is therefore roughly three credits for one run, not one credit because it was one business event. Choose Core, Pro or Teams and a monthly credit volume; the pricing slider lowers the cost per 1,000 credits at larger volumes. We would count a normal month of actions before paying for capacity, then check whether Pro’s priority execution or Teams’ roles are required. The facts here are from Make’s own pages, checked on 30 Oct 2026, not a workflow we have tested hands-on.

For a proposed first scenario, use safe sample data and verify the destination record. A successful connection isn’t enough if the wrong field is updated.

How Make credits behave in a real month

Since 27 August 2026 credits are Make’s billing unit. Most module actions use one credit, while the router and error-handler modules are free, so a well-built scenario with branches doesn’t cost more just because it has branches. Some advanced features that use Make’s own AI provider can use more than one credit per action.

What happens when credits run out is worth knowing before the first busy week. Make’s pricing FAQ says scenarios stop running. Incoming webhooks are queued up to the plan’s queue limit, and scheduled scenarios that poll an app pick up the missed data once credits are available again. On Core, Pro and Teams you can buy extra credits in bundles of 1,000 or 10,000 at your plan’s rate, or turn on auto-purchase of 10,000 credits. Plan credits expire at the end of each term, so buying a much larger volume “just in case” isn’t money saved.

Each plan also has a usage allowance that grows with the credit volume. For every 10,000 credits Make lists 5 GB of data transfer, 10 MB of data storage and a webhook queue of 667 items. A scenario that moves files or large payloads can hit the transfer allowance before it runs out of credits.

Changing or cancelling a plan

Downgrading takes effect straight away and starts a new billing cycle. Any active scenario that relies on a feature from the higher plan stops running. Make says it warns you before the downgrade completes, and unused credits move to the new subscription. Cancelling keeps the paid plan until the end of the term and then moves the organization to Free, with its limit of 1,000 credits and two active scenarios.

Make offers a Start-up Plan for companies with fewer than 20 employees, advertised at 50% off for those who qualify, and asks non-profits to contact it about discounts. Core, Pro and Teams can be paid by card, ACH direct debit or Google Pay; wire transfer after invoice is for Enterprise. The plan prices in the summary above are from our 30 October check; Make’s plan cards didn’t load in our 13 November fetch, so confirm the price for your credit volume on the pricing slider before paying.

Apps, data stores and custom connections

Make lists integrations with more than 1,000 third-party apps out of the box. If a tool you rely on isn’t there, a custom app can connect Make to almost any service with a public API, which is useful for a niche booking system or an in-house database. Make itself can be managed through more than 300 REST API endpoints, so an agency running scenarios for several clients can script routine changes instead of clicking through each organization.

Data stores are Make’s small built-in tables for things like a list of processed order IDs. An organization can have up to 1,000 of them on any plan, but the storage behind them follows the credit volume: 1 MB for every 1,000 credits, and each data store takes at least 1 MB. On Free that means one data store. Anything larger, such as a customer list, belongs in a proper database or spreadsheet that the scenario reads from.