Make Review (2026): Visual Automation With Power, a Learning Curve and a Credit Meter

Make is a visual automation platform that connects apps through workflows it calls scenarios. It sits between simple “if this, then that” tools and custom code: you can see how data moves, add branches, and transform records without writing every step yourself.

What Make does

You build a scenario on a visual canvas by chaining modules. A module is one step, such as reading a spreadsheet row, sending a message or calling an API. A scenario usually starts with a trigger, transforms data, then sends it to another app. Routers and filters let a scenario branch; iterators and aggregators help process groups of records. Make also provides HTTP requests, webhooks, custom apps, data stores and an API for managing the platform.

Make’s AI features include AI agents, the Make AI Toolkit, an MCP server for connecting AI tools to scenarios, and Maia, a conversational automation builder. Make lists these on every plan, with the AI agents still marked as beta. Make says paid plans can connect their own AI provider, such as OpenAI or Anthropic, and pay that provider directly for token use.

How pricing and credits work

Plans and prices in this section follow Make’s official pricing page as checked on 17 October 2026.

Make bills in credits. Most module actions consume one credit, including reading, searching, creating, updating and deleting data, transforming data and iterating. The Router module and error-handler modules (Rollback, Break, Resume, Commit and Ignore) do not consume credits. The Make Code app, which is not available on Free, costs two credits per second of execution on paid plans, and some AI features may use more than one credit.

That means costs depend on how many steps run and how often a scenario runs. A five-step scenario that runs 100 times uses roughly 500 credits, before retries or other branches. Scheduled polling can spend credits checking for new data even when there is nothing new; use a webhook where the app supports one and it fits your workflow.

At 10,000 credits per month, Make lists Free at $0, Core at $9, Pro at $16 and Teams at $29 per month. These are annual-billing rates, which is how the pricing page displays them by default; monthly billing costs more, so check the billing toggle on the page. Higher credit tiers are available on paid plans, with Core capped at 300,000 credits and Pro and Teams supporting up to 8 million credits per month.

• Free: 1,000 credits a month, two active scenarios, a 15-minute minimum interval between scheduled runs, a five-minute maximum run, and no time limit.
• Core: unlimited active scenarios, one-minute scheduling, a 40-minute maximum run, files up to 100 MB, increased data transfer and Make API access.
• Pro: priority scenario execution, custom variables, full-text execution-log search, and annual prepaid credits that last 12 months.
• Teams: team roles and shareable scenario templates.
• Enterprise: custom pricing, with features including SSO, overage protection, audit logs, custom roles and 24/7 support.

Limits worth knowing

• Credits expire. Unused credits expire at the end of the term: monthly, or after 12 months on annual Pro, Teams and Enterprise plans. Annual Core credits still expire monthly.
• Scenarios stop at the limit. Make notifies customers at 75% and 90% usage. Webhooks can queue within the account’s available allowance, and polling scenarios search for records since their last successful run once credits return. On Core, Pro and Teams you can turn on auto-purchase, which buys an extra 10,000 credits when you run out. Overage protection is an Enterprise feature.
• Extra credits cost more. Make says purchased extra credits, manual or automatic, include a 25% surcharge over credits included in the plan.
• Usage allowances scale with credits. Data transfer is 5 GB per 10,000 monthly credits, so file-heavy scenarios may hit that limit. Maximum file size also depends on the plan.
• Downgrades can stop scenarios. Active scenarios that use features from a higher plan are stopped.

What users report

Third-party review platforms are broadly positive, with reviewers often praising the visual builder and range of integrations. Other reviewers describe a learning curve that steepens with advanced features, errors that can be difficult to diagnose, and credit usage that is less predictable than a flat per-task model. Trustpilot reviews also mention support responsiveness and billing disputes.

Security and data handling

Make’s security page lists GDPR adherence and completed SOC 2 Type II and SOC 3 audits. Make hosts on AWS in the EU and North America. Make also says its Enterprise platform runs in a separately managed AWS environment, isolated from self-service customers, under an ISO 27001 certified security program. Enterprise adds controls such as company SSO and overage protection. Security teams can request current reports and confirm the controls and data-region terms that apply to their account.

Who Make suits

Make is a strong candidate for freelancers, agencies, marketers and operations teams that need conditional branching, data transformation and multi-app workflows—and are willing to learn a capable but more involved interface. Its unlimited-user policy can also suit teams that share access without paying per seat.

Who should look elsewhere

• Beginners with simple needs. A simpler automation tool may be faster to learn for basic two-app workflows.
• Teams that need predictable billing. Credit use varies with workflow design and volume; scenarios stop when credits run out unless you buy extra credits at a surcharge or are on Enterprise with overage protection.
• Step-heavy, low-frequency workflows. A service that counts a complete workflow as one execution may be cheaper for a long scenario. Compare with your own run volumes and current plan limits.

What to verify before you buy

1. Confirm current prices and the billing period on Make’s official pricing page, using both the monthly and annual views.
2. Estimate credits using records × modules per record × runs per month, with headroom for retries and branches.
3. Check that the apps you depend on have the modules and triggers your workflow needs.
4. Check whether webhooks can replace polling for important triggers.
5. Decide whether you want extra-credit auto-purchase, and remember it carries a 25% surcharge.
6. If you need SSO, overage protection or audit logs, confirm Enterprise terms with Make.

Bottom line

Make offers a capable visual automation builder and a free plan that is useful for learning and smaller workflows. Its strengths are branching flexibility and broad integrations; the trade-offs are a learning curve and usage-based credit costs that require monitoring. Try a representative workflow on the free plan, check its execution history and credit use, then compare the actual monthly pattern with paid-plan limits.