Make Pricing: Free, Core, Pro, Teams and Credits
Compare Make Free, Core, Pro, Teams and Enterprise prices, credit limits, AI usage costs, extra-credit rules and monthly versus annual billing.

See the Make Toollers product profile for the catalog identity.
Quick verdict
Key takeaways
- Free: 1,000 credits and two active scenarios
- Core: $12 monthly at 10k credits
- Pro: $21 monthly at 10k
- Teams: $38 monthly at 10k
- Enterprise: custom quote
- Ordinary module operations generally one credit
- AI may use dynamic credits
- Extra credits and expiration rules
- Annual discount differs
Visual automation scenarios with routers, data transformations, AI modules and usage-based execution credits.
Best for: Operations specialists and technically comfortable marketers automating multi-app processes with branching logic, API calls and detailed data transformations.
- Make AI Agents beta
- Full-text execution log search on Pro
- Annual pooled credits on Pro and Teams
- Conditional route filters
- Unlimited active scenarios on Core and up
- Visual canvas supports branching, filters, iterators and transformations in complex workflows.
- Free plan includes 1,000 monthly credits and core scenario-building tools.
- Core starts at $12/month for 10,000 credits with unlimited active scenarios.
- Most module actions consume credits; iteration, aggregation and advanced AI/code actions can increase usage.
- Free plan is limited to two active scenarios and 15-minute scheduling.
| Plan | US monthly displayed price | Credits at shown configuration | Selected features and limits |
|---|---|---|---|
| Free | $0 | 1,000/mo | Two active scenarios; 15-minute minimum schedule |
| Core | $12/mo | 10,000/mo | Unlimited active scenarios; 1-minute schedule; Make API |
| Pro | $21/mo | 10,000/mo | Priority execution; custom variables; full-text log search |
| Teams | $38/mo | 10,000/mo | Team roles and shared templates |
| Enterprise | Contact sales | Negotiated | Audit logs; advanced app and security policies |
| Annual billing | Live checkout discount | Depends on tier and term | Prepaid term and different expiration rules |
Pros
- Permanent Free tier
- Public monthly price examples
- Visual routers and transformations
- Upgradeable credit bands
- Paid one-minute schedules
- Enterprise governance
Cons
- Credit counts can rise with bundles
- AI usage can be dynamic
- Extra credits may expire
- Free two-scenario and timing limits
- Annual billing and refund terms require review
Who should use this
- Free: limited experimental integrations
- Core: more active production scenarios
- Pro: operator needing logs and variables
- Teams: shared maintenance
- Enterprise: formal audit and governance
- Buyer able to forecast operations
Who should avoid this
- Buyer counting one credit per complete scenario
- Team unable to monitor AI consumption
- User requiring instant behavior from Free polling
- Organization assuming unused credits always roll over
- Purchaser ignoring contract and extra-credit terms
Make uses credits to bill for workflow automation. Its US public plan selector shows a permanent Free tier with 1,000 monthly credits and paid Core, Pro and Teams tiers. At the displayed 10,000-credit monthly configuration, the prices are $12 Core, $21 Pro and $38 Teams per month. Enterprise is quoted.
Those are monthly-plan reference prices for the shown credit volume, not every available configuration. Changing the credit slider or choosing annual prepayment changes the price. Credits can also be consumed in different quantities by AI features, modules, transformations and loops, so the number of workflows alone does not define the bill.
We checked Make's official plan page, credit documentation, extra-credit rules and subscription help on November 7, 2026. This is a documentary pricing guide, not a charged invoice or an account-tested calculation. Regional tax, renewal terms and dynamic checkout offers still require verification before buying.
Make plans and current monthly prices
Free: $0 for 1,000 credits monthly
Free has no time limit and includes up to 1,000 credits per month. It offers the visual scenario builder, standard application connections, routers and filters. The current plan table lists at most two active scenarios and a 15-minute minimum interval between scheduled runs.
A single scenario can use several modules, with each ordinary operation generally costing one credit. A free account receiving 200 orders and performing two counted operations per order could spend roughly 400 credits on those operations. This calculation excludes any separate trigger checks, special AI credits or retries.
Free is suitable for learning the interface, creating a small data sync or observing whether the exact connector works. The 1,000-credit limit and schedule interval make it less appropriate for frequent time-sensitive processing. Its lower execution time and file-size ceilings can also affect real workloads.
The current matrix lists a five-minute maximum single-scenario execution time and a five-megabyte file limit on Free. Larger files or slower processing may require an upgrade, a smaller input or a different architecture. These are distinct constraints from the monthly credit balance.
Core: $12 monthly at 10,000 credits
The displayed US monthly Core reference is $12 for 10,000 credits. Core removes the two-active-scenario ceiling and allows schedules as frequent as one minute. It also adds Make API access and increased data-transfer capacity at the reference credit level.
For a monthly subscriber remaining at the same selected 10,000-credit tier, twelve monthly charges would total $144 before taxes and extra credits. That is arithmetic, not an annual-plan quote; Make offers a separate discounted annual billing choice.
Core is a logical first paid tier when several routine scenarios run across spreadsheets, CRM systems, forms and notifications. It does not include every advanced observability or team management feature. The important question is whether 10,000 credits covers the complete module workload at its busiest point.
Pro: $21 monthly at 10,000 credits
Pro's displayed monthly reference is $21 for 10,000 credits. It builds on Core with priority scenario execution, custom variables and full-text execution-log search, according to the official plan matrix. These features help when many workflows need troubleshooting or shared configuration values.
Twelve full monthly charges at this unchanged entry tier would be $252 before tax and variable usage. Again, this is a monthly-billing illustration, not a discounted annual commitment. Higher credit bands can change the underlying subscription price.
Pro can fit an operator who needs to inspect runs often and maintain a complicated collection of scenarios. Paying for Pro solely to get more credits may be unnecessary if a larger Core credit tier already covers the workload; compare the tier and feature changes separately.
Teams: $38 monthly at 10,000 credits
The official price selector shows Teams at $38 monthly for the 10,000-credit configuration. Its distinctive additions include teams, role management and shared scenario templates. It is aimed at groups building and maintaining automations together rather than one owner handling every connection.
Twelve monthly payments at that listed level would be $456 before taxes and extra consumption. This figure assumes the selected configuration stays unchanged. Annual prepaid pricing, if chosen, should be taken from Make's live checkout rather than inferred from a generic discount percentage.
Teams is useful when staff need appropriate access and collaboration boundaries. Its extra team features do not make all actions free or turn 10,000 credits into a separate allowance for every member. Estimate organization-wide usage and confirm permission rules.
Enterprise: a negotiated quote
Enterprise is quote-based and includes additional integration, governance and support features. Make lists advanced security, organization controls, audit logs, enterprise app access, custom functions, support and overage protection among its enterprise capabilities.
The actual price depends on negotiated use, selected credit volume and business terms. It is not responsible to invent an Enterprise per-seat rate from a lower self-service plan. Request written details for the chosen deployment, data controls, support hours, ownership and excess usage.
Make also advertises a Start-up Plan opportunity for eligible smaller companies, including an indicative 50% discount on Business for organizations under 20 employees. Eligibility and actual pricing require a direct offer and must not be applied automatically to Core or Pro calculations.
What is a Make credit?
Make moved from an operations-only billing label to credits in August 2025. For most non-AI module operations, the official help says one operation equals one credit. Reading a record, making an HTTP request, adding a row or updating an app object can each generate its own credit usage.
Counting a completed scenario as one credit would therefore be wrong. A trigger may retrieve several bundles and feed them through multiple modules. Each performed action, transformation or iteration can add usage, especially when one source event contains numerous records.
The official pricing FAQ gives examples such as searching an app, deleting a record, transforming data and aggregating values as credit-consuming actions. A router or certain error-handling controls are exceptions and do not consume a credit merely for acting as a routing control.
A complex scenario may use only a few credits for a simple event or hundreds for a large list. The model is flexible, but buyers must build estimates from executed modules, not from the visual number of boxes alone. Branches that do not run do not incur their downstream module work.
AI modules can use dynamic credits
Make's credits guide distinguishes fixed usage from dynamic usage. Certain built-in AI tools and automatic provider connections can consume credits based on tokens, file size, page count or processing time. These charges may exceed one credit for a single module execution.
When a business brings its own external AI provider connection, Make commonly charges operation credits while the provider separately bills for model tokens. Using Make's own AI Provider can roll model consumption into Make credits based on the provider and model class.
The billing unit is therefore different for two workflows with identical diagrams. A short classification prompt on a small model might use far fewer credits than a large document extraction with long model output. Do not multiply one credit by the number of AI steps and treat it as a guaranteed total.
The vendor can update model-specific token conversion rates. When forecasting costs, save the effective rate for the selected model and provider and compare it with recent usage. Also budget external model invoices or data-service charges that Make does not absorb into its own subscription.
Worked example: two-app lead intake
Suppose 300 lead submissions each month require one counted CRM contact creation and one counted team notification. Those 600 ordinary operations would use approximately 600 credits, assuming the trigger and any transformations do not add separately counted work under this example.
That amount is within Free's 1,000 monthly credit bucket, but the Free plan also limits active scenarios and schedule frequency. A 15-minute polling interval may be insufficient for a sales team expecting near-immediate lead response, even while the credit arithmetic looks affordable.
If each lead also requires a lookup and a record update, the counted operations could rise to about 1,200 for those four actions. That exceeds Free and makes an appropriate paid credit tier more plausible. Real scenario history should confirm the exact module counts.
Worked example: order synchronization
Consider 750 monthly orders. Each order results in three counted module operations: retrieve details, write to a database and send a notification. The illustrative total is 2,250 credits, apart from additional polling, branching or error recovery.
At the listed 10,000-credit Core tier, that hypothetical workload fits with room for other scenarios. The $12 monthly subscription reference is therefore an entry point for comparison, provided the chosen integrations, schedule limits and data-transfer entitlements support the process.
Now imagine each order contains four line items that each require two further module operations. Eight more operations per order would add 6,000 credits, bringing the simplified model to 8,250. A modest change in data structure can move usage close to the allowance.
At ten line items per order, the same repeated actions would add 15,000 credits and exceed the 10,000-credit entry tier even before the basic operations. Use actual order distributions rather than an average that hides the busiest customers.
Worked example: AI-enriched tickets
Assume a support workflow receives 400 tickets monthly and uses one ordinary input lookup and one ordinary destination update per ticket. Those two actions would account for around 800 credits before the AI enrichment stage and any other charged modules.
The AI stage's cost cannot be assigned reliably without the chosen provider, connection, model, prompt length, response length and official rate. It may be fixed or dynamic. Capture its projected token and credit usage through an authorized pilot before deciding whether 1,000 or 10,000 credits is sufficient.
These examples are arithmetic, not screenshots or observed executions. A real workflow may have extra calls, skipped branches, repeated bundles, retries and files that change consumption. Cost forecasting should have a peak-month buffer and a budget owner.
Do unused Make credits roll over?
The official FAQ says ordinary credits expire at the end of the subscription term, with annual and monthly credits handled under the plan's billing arrangement. Make also has plan-specific flexibility for credits on eligible annual Pro or Teams arrangements.
Annual subscriptions are prepaid and differ from twelve independent monthly purchases. The latest monthly-and-annual guide describes annual credit allocations for applicable plans; Core's annual credit reset behavior can differ. Read the relevant plan and credit expiry rules before paying upfront.
Purchased extra credits also have expiration terms. Make's extra-credit help specifies that Core with annual billing still resets regular and extra credits monthly. Do not assume that a purchase late in one month automatically rolls into a future year.
Unused capacity is not a financial asset that can always be carried forward. For uneven seasonal demand, compare whether the annual credit flexibility genuinely helps the selected plan and whether a smaller tier with occasional extra credits costs less.
Extra credits, automatic purchasing and interruption
When the balance runs out, Make says scenarios stop until credits are added or the subscription changes. Incoming webhooks may queue within allocated storage capacity; polling scenarios can later search for changes since a previous run. Those recovery behaviors are subject to limits.
The vendor permits manually buying extra credits or using auto-purchasing on eligible paid plans. The FAQ describes bundles of 1,000 or 10,000, and the extra-credit guide states that these purchases can carry a plan-dependent premium over ordinary credits.
Auto-purchasing can prevent interruption but introduces variable costs. Before enabling it, inspect the current unit rate, purchase increment, maximum allowed auto purchases and payment method. Establish who approves additional purchases and who is alerted before the normal allowance is exhausted.
For critical automations, decide which failure is worse: a pause during a traffic spike or an unexpected bill. A hard cap can control cost but may delay customer orders, document processing or internal notifications. Neither policy is universally correct.
Other limits that affect pricing value
At the listed 10,000-credit tier, Make describes 5 GB of data transfer and proportional storage entitlements. Its FAQ also discusses incomplete-execution storage and webhook queue capacity. Large attachments and long execution histories can require attention even when monthly credits remain.
The current plan table lists smaller files on Free and larger allowances on Core, Pro and Teams. Maximum scenario runtime, API access, execution log retention and the minimum schedule interval also differ. These limits can determine the appropriate tier before credit usage does.
An organization that only processes a few records might still need Pro's advanced logging or Teams' sharing. Conversely, a single operator processing many records might need higher credits without needing collaboration. Separate capacity needs from permission and observability needs.
Monthly versus annual billing
Make advertises a discount for paying annually in advance. The live selector lets buyers choose monthly or annual terms, and the exact savings may depend on plan and selected credit volume. The $12, $21 and $38 references here are monthly-billing prices at 10,000 credits.
Multiply the monthly price by twelve only to illustrate twelve unchanged monthly charges. Do not present that result as an annual invoice. A true annual quote may have different credit allocation, renewal timing and cancellation effects.
The official cancellation FAQ says a paid plan normally continues through the current month or annual term before switching to Free, subject to account configuration. The subscription-change documentation separately describes a no-cash-refund policy and plan-transition terms.
Review taxes, currency, charge dates, renewal, unused credits, data retention and downgrade restrictions before signing. Make says active scenarios using higher-tier features may stop after a downgrade. A lower subscription price can therefore change production behavior.
Which Make tier is appropriate?
Choose Free for initial evaluation and a small number of low-volume workflows that tolerate the schedule and execution limits. Choose Core when unlimited active scenarios, one-minute schedules and 10,000 or more selected credits fit a single team's routine work.
Pro is worth comparing when custom variables, priority execution and full-text log search improve support of the workflow estate. Teams is intended for groups that need roles and shared templates. Enterprise is relevant where advanced permissions, audit logs and bespoke contracts become mandatory.
The biggest mistake is buying from the headline monthly price without counting all operations. Build an itemized scenario budget, check the source apps' own API and subscription limits, and forecast the normal and peak months separately.
Competitor context and research limits
Zapier uses successful task actions, with selected AI multipliers and overage rules. Pabbly Connect promotes different workflow packages and lifetime offers. Gumloop emphasizes agent-driven execution with its own credits and orchestration fees. The billing units are not interchangeable.
Make's visual scenarios may make complex branching easier to reason about, but a diagram alone does not verify execution reliability or integration completeness. Confirm the actual source and destination capabilities in the product before replacing a working process.
Our price references and feature mapping came from vendor-owned pages reviewed on November 7, 2026. We did not purchase a plan, process a sample record, contact support or receive a customized invoice.



