What Is Make? Visual Automation Billed in Credits

The short answer: If someone on your team copies leads, orders or report rows between apps every week, Make is a visual builder that does the copying on a schedule or the moment the data arrives, and its Free plan includes 1,000 credits a month to prove the first flow (pricing page). It can also run an AI agent inside a flow, so a model chooses one step while the rest stays fixed.

Disclosure: I may earn a commission through some links on this site. It does not change what this page says.

Before you pick a plan:

1. Count credits per module, not apps per flow. An operation is counted each time a module processes a bundle, a trigger once per run, and one operation is one credit for non-AI apps (operations guide, credits). For example, a trigger and four modules is 5 operations per lead, so 200 leads a month = 1,000 credits, the whole Free allowance.
2. Start from the apps you already pay for. Check that your CRM and form tool have native modules among the 3,000+ the homepage lists (Make).
3. Know where you will read the result. Every run's status, operations and credits sit in the scenario's History tab (scenario history).

What Make does

A scenario is a chain of modules that moves and transforms data between services (first scenario guide). A trigger starts it, by polling on a schedule or instantly through a webhook; routers split it into branches and filters stop bundles that fail a condition (router, filtering).

The Run an agent module adds a model with instructions and tools, which can be modules, whole scenarios or MCP servers (agent guide); Make labels that app an open beta (app reference). The Make MCP server works the other way round, letting Claude or ChatGPT run your on-demand scenarios (MCP server).

Who it fits, and who it frustrates

It fits a lead who thinks in steps and wants to see every branch without writing code. It frustrates a team that wants a flat bill, because credits rise with every bundle and AI modules on Make's own AI Provider also charge for tokens (credits). Give each scenario an owner: one that starts with an instant trigger is switched off at its first error (scenario settings).

Plans and price

The pricing page names Free, Core, Pro, Teams and Enterprise, but draws the paid prices in the browser behind a bot check, so they could not be read from the vendor on 24 October 2026 and are left out here. Its text does state that every 10,000 credits a month brings 5 GB of data transfer and a webhook queue of 667 items, that credits expire at the end of the term, and that yearly prepayment costs less than monthly billing.

A credit slider is built to make the tier above yours feel like insurance. Size the plan from the credits column of one real week in History instead.

Next to n8n, Pabbly Connect and Zapier

Prices in this list were checked on 24 October 2026 on each vendor's pricing page.

• n8n bills one execution per complete run, however many steps it has, from $24 a month on monthly billing for 2,500 executions, and can be self-hosted (n8n pricing).
• Pabbly Connect bills only action steps, so triggers, filters and routers are free, and sells an Unlimited plan at $79 a month on monthly billing (Pabbly pricing).
• Zapier uses tasks for every step in a Zap, with Professional from $29.99 a month billed monthly.

Getting started

How to use Make builds a lead-routing scenario with an AI agent step from Make's help centre. If the trouble is five tools doing overlapping jobs rather than Make itself, the Startup Fixer, a one-week stack review I sell, is built for that question.

FAQ

Is there a free plan?

Yes: 1,000 credits a month with 1 MB of data storage, per the pricing page. The agent app runs on it with Make's AI Provider; OpenAI or Claude connections need a paid plan (agent guide).

What happens when the credits run out?

Scenarios stop until credits are added, and incoming webhooks wait in a queue until they resume, according to the pricing page.

Can Make keep personal data out of its logs?

Yes. Keep data confidential records that a run happened but not its payload (scenario settings).