Research checked 27 August 2026 against Make’s official public pages. This is educational information, not personal testing, a recommendation for every business or a promise of savings or results. Pricing, features and programme terms can change.
In brief
Make is a hosted automation platform for building workflows, which it calls scenarios, from connected modules. Its official product page describes a visual, no-code builder, data transformation, routers, filters, webhooks and connections to more than 3,000 pre-built apps. It also supports custom API requests and AI-related features. See Make’s official product overview.
It may be worth investigating when a workflow needs several steps, branching logic or data transformation across different services. That flexibility also increases the need to understand module behaviour, permissions, credit use, error handling and ownership. A visual canvas does not remove the underlying technical or data-protection responsibilities.
Who may find it suitable?
Make may be a practical candidate for a small business that:
- needs to move or transform information between supported cloud services;
- wants to see multi-step logic and branches on a visual canvas;
- can assign a named owner to monitor failures and maintain connections;
- is willing to measure real credit usage before committing to a plan; and
- can test with low-risk data before using the workflow in a live process.
Examples to investigate include routing enquiries, updating approved records, sending internal notifications or coordinating repeat administrative steps. These are examples, not claims that every process or app will work as required.
When to pause or consider another approach
Make may be a poor fit where no supported module or workable API exists, a process requires strict real-time performance, the organisation cannot accept a hosted third party handling the data, or nobody can maintain the automation. A manually checked process may remain safer for low-volume, high-consequence work.
Do not assume that an app name in the catalogue proves every required action, field, permission or regional feature is supported. Check the exact modules, authentication method, API limits and test-account behaviour before moving a live process. If a workflow handles special-category personal data, payment information, legal decisions or safety-critical actions, obtain appropriate security, privacy and professional review first.
How Make’s credits work
Make now uses “credits” as its billing unit. For most non-AI apps, one module operation uses one credit. Some AI and advanced features use credits dynamically, and a third-party AI connection can create a separate bill from the AI provider for token usage. Make documents these distinctions in its official credits guide.
A scenario run does not necessarily equal one credit. A workflow that retrieves a record, transforms it and updates two systems can perform several module operations. Repeated bundles, loops, retries, polling and AI processing can increase usage. Estimate cost from representative executions and the scenario history rather than from the number of scenarios alone.
If a paid plan runs short, Make says an account can upgrade, buy extra credits or enable automatic extra-credit purchasing on eligible plans. Automatic purchasing can prevent interruption but also creates a spend-control risk. Decide who can enable it, set internal usage thresholds and review unexpected increases.
Current plan snapshot
When checked, Make’s official pricing page showed the following US-dollar examples at the 10,000-credit level:
- Free: $0, with up to 1,000 credits per month, two active scenarios and a 15-minute minimum interval between scheduled runs.
- Core: $10.59 per month on monthly billing, or $9 per month equivalent on the annual view. It adds unlimited active scenarios, scheduling down to one minute and Make API access.
- Pro: $18.82 per month on monthly billing, or $16 per month equivalent on the annual view. It adds priority execution, custom variables and full-text execution-log search.
- Teams: $34.12 per month on monthly billing, or $29 per month equivalent on the annual view. It adds teams, team roles and shared scenario templates.
- Enterprise: custom pricing, with additional governance, security and support features listed by Make.
UK pricing caveat: these are a dated snapshot of the US-dollar values served during research, not a quote. Annual pricing involves annual commitment or prepayment, and displayed prices, exchange rates, VAT or other taxes, credit allowances and plan features may differ at checkout. Select the intended billing frequency and credit volume on Make’s current pricing page before deciding.
Practical limitations to model
- Credit variability: branches, bundles, retries and dynamic-credit features can make actual consumption differ from a simple module count.
- Service dependency: scenarios depend on Make and every connected provider. API changes, rate limits, expired authentication or outages can interrupt a workflow.
- Partial completion: an early step may succeed before a later step fails, leaving systems out of sync. Design for duplicate prevention, safe retries and reconciliation.
- Plan limits: scheduling intervals, active-scenario limits, execution time, storage, data transfer, API access and support vary by plan and credit allowance.
- Maintenance: fields, permissions and business rules change. Document the workflow, owner, dependencies, alert route and manual recovery process.
Make’s documentation says incomplete-execution storage is disabled by default. If enabled, unfinished runs can be held for review or retry, subject to storage limits. Error handlers can change whether an error is ignored, retried, committed, rolled back or queued for intervention. Review the official error-handling overview and test the chosen behaviour rather than relying on a successful “happy path”.
Security and permissions checklist
Make’s security page states that its information-security programme is ISO 27001 certified, that it has completed SOC 2 Type II and SOC 3 audits, and that it uses AES-256 encryption at rest and TLS 1.2 or 1.3 for network communication. These provider statements are useful evidence, but certifications do not decide whether a particular workflow, data set or account configuration is appropriate for your business.
- List each data field entering Make, where it is sent and whether it appears in logs or stored incomplete executions.
- Review Make’s current privacy notice, data-processing terms, subprocessors, hosting choices and retention controls against your UK GDPR obligations.
- Grant only the scopes and folders the workflow needs. Prefer dedicated business connections or service accounts where the connected provider supports them.
- Do not send passwords or API keys through email or workflow notes. Record who can create, edit, run, export and delete scenarios and connections.
- Enable appropriate account protections, remove leavers promptly and schedule reviews of connections, access and unused scenarios.
- Check plan-specific controls such as team roles, SSO and enterprise governance rather than assuming they are included at every tier.
A safer evaluation process
- Map the workflow. Write down the trigger, inputs, actions, outputs, exceptions, owner and manual fallback.
- Check exact support. Confirm every required app module, field, permission, webhook or API endpoint.
- Use test data. Start with non-sensitive sample records and a separate test destination where possible.
- Test failure modes. Simulate missing fields, duplicates, expired connections, rate limits and an unavailable downstream service.
- Measure credits. Run representative volumes, including loops and retries, then model a busy month with headroom.
- Add controls. Configure filters, validation, alerts, error handling, spend reviews and approval steps for consequential actions.
- Document recovery. Keep a record of connections, data mappings, rollback or reconciliation steps and who is responsible.
- Review after launch. Monitor failures and usage, sample outputs, and re-check the workflow when an app or business rule changes.
For a platform-neutral starting point, use the no-code automation checklist.
Affiliate disclosure
The button below is a Make affiliate link. If you register through it and later make an eligible subscription payment, UK Digital Tools Research may receive a commission, at no extra charge because of the link. This commercial relationship does not show that Make is suitable for your business.
Make’s current public terms state 35% of eligible subscription payments for 12 months, starting when the referred user registers. They describe a 30-day window after the click in which the visitor must register, and exclude purchases of extra operations (now described as credits) from commission. One separate answer on Make’s affiliate page mentions 24 months; Make’s dedicated commission answer and help documentation both state 12 months, so this guide uses the narrower term. Attribution and payment remain subject to Make’s current tracking and terms. See Make’s public affiliate page, affiliate help documentation and this site’s full affiliate disclosure.
Check the current plan, billing frequency, credit allowance, taxes, renewal terms and any offer shown at registration. No promotional saving or result is guaranteed.