Make.com Review 2026: Credit Pricing, Plans, and Buyer Fit

Limits: No Make account was purchased, so scenario building, credit burn, AI credit usage, execution priority, support, and the on-premise agent were not tested by us. Make's own pricing page returned HTTP 403 (Cloudflare bot protection) during research on September 22, 2026. Dollar figures therefore come from Make's Help Center examples plus third-party trackers that state their read dates (September 14 and July 28, 2026). Confirm current numbers on the live pricing page. Third-party trackers disagree on the exact monthly-billing prices and on one alternative annual ladder. This review reports the annual figures that match Make's own Help Center example and flags the conflicting set. Free plan limits (1,000 credits, two active scenarios, 15-minute minimum interval) are third-party sourced because the official pricing page could not be fetched. The most detailed third-party pricing tracker used here is published by Latenode, a competing automation vendor. Its figures are cited only where they agree with other sources or with Make's own documentation. Third-party sources also disagree about credit rollover behavior, so this review does not make a rollover claim and covers only Make's documented extra-credit expiry rules.

Make is a visual automation platform where you assemble scenarios from triggers, modules, and routers instead of writing code. Its billing unit is the credit, renamed from operations in 2025, and the model is what buyers most often underestimate: most ordinary modules cost one credit per operation, but polling checks, failed runs, and Make’s own AI features can consume credits in ways a flat per-task price does not. [S1][S5][S6]

This is a desk-research review built from Make’s Help Center documentation and three independent pricing analyses published between July and September 2026. No account was purchased, no scenario was built, and no credit burn was measured. Make’s public pricing page is behind Cloudflare bot protection and returned HTTP 403 during research, so the dollar figures below come from trackers that state their read dates plus an official Help Center example, and the limitation is flagged where it matters. [S5][S6]

Bottom line

Verdict: conditional. Make is a strong pick for branching, multi-step automation with a visual canvas, and at the annual rate its entry plan is cheap relative to task-priced competitors. The credit system is the catch, and it is a real one: independent analyses describe unpredictable AI credit consumption, credits spent on polling triggers that find nothing, and overage credits that cost 25 percent more than the credits included in your plan. Buyers who track their burn rate and design scenarios around it get good value. Buyers who expect a flat monthly bill do not. [S2][S6][S7]

Make.com pricing in 2026

Make sells a free tier plus Core, Pro, Teams, and a quote-based Enterprise plan. Each paid plan is priced by the monthly credit volume you choose, so the numbers below are the first rung of a ladder rather than the whole product. At the 10,000-credit tier, the third-party figures read from Make’s pricing page on September 14, 2026 are: [S5][S6]

Two source notes on this table. First, Make’s own Help Center confirms the shape of the entry tier: its extra-credits documentation works through an example of “a $9 plan” with 10,000 credits, which puts the annual Core figure on official footing. Second, some third-party trackers instead quote an annual ladder of roughly $12, $21, and $38 with monthly prices near $16, $28, and $51. That set is about a third higher than the figures above and does not reconcile with Make’s own $9 example, so it is flagged here rather than blended in. Confirm the live numbers before you buy. [S2][S5]

Annual billing is advertised by third-party trackers as roughly 15 percent cheaper than paying month to month, and the 25 percent premium on extra credits applies either way. Above 300,000 credits per month, Make no longer offers Core at all: its November 2025 pricing update moved those tiers to Pro, capped Core at 300,000 credits, and extended Pro to 8 million credits per month. Buyers who outgrow Core are pushed up a plan rather than across a slider. [S2][S3][S5][S6]

How credits are actually spent

The credit model is documented in Make’s Help Center and it is more nuanced than “one module, one credit”: [S1][S5][S7]

• Non-AI modules consume one credit per operation by default, and third-party AI apps such as OpenAI or Anthropic also bill one credit per operation, with you paying the AI vendor directly for tokens.
• Make’s own AI provider is different: credits are based on tokens and operations, so cost scales with prompt size, file size, page count, or processing time.
• Some modules are fixed above the default. Make AI Content Extractor modules, for example, consume 2 or 10 credits per operation depending on the module.
• Routers and filters do not consume credits on their own, but bundles multiply: five input items passed to two action modules produce ten operations, not two.
• Polling triggers spend a credit on every check, including checks that find nothing new. A scenario that polls every 15 minutes runs 2,880 checks in a 30-day month before any real work happens.
• Failed runs consume credits too, which is one of the most common complaints from long-term users.

A worked example from the same analysis: a trigger that receives one lead, writes one CRM record, and posts one Slack message costs about three credits per run, so 1,000 runs fit inside Core’s 10,000-credit allowance at the annual rate. The same workflow with polling and looping can leave far less headroom, which is why reviewers consistently say the plan matters less than the scenario design. [S5][S7]

Extra credits, overages, and expiry

Make does not simply stop when you run out. On a paid plan you can buy extra credits manually, or enable auto-purchasing so scenarios keep running. The rules are published and consistent: [S2][S3]

• Extra credits cost 25 percent more than the credits included in your plan, whether purchased manually or automatically. Make standardized this on November 6, 2025, when manual purchases stopped being free of the premium.
• Auto-purchasing buys in units of 10,000 credits and is capped at the number of credits in your subscription. An 80,000-credit plan can auto-purchase at most eight times.
• Extra credits expire at the end of the current billing cycle on monthly plans, and at the end of the billing year on annual plans, except that Core on annual billing resets monthly and takes purchased extras with it.
• Extra credits include additional data transfer allowance, but they do not change other plan limits.
• The official example prices the math: on a $9 plan with 10,000 credits, one credit costs $0.0009, and 10,000 extra credits cost $11.25.

The practical implication is that running out is a spending event rather than an outage, and the cost per credit is worse than your plan rate. Make’s own documentation recommends moving to a higher tier, where per-credit costs are lower, if you are regularly buying extras.

Free plan limits

The free tier is genuinely free rather than a trial, but its boundaries are tight: 1,000 credits per month, two active scenarios, a 15-minute minimum interval between scheduled runs, and no credit card required. Independent trackers agree on those three limits. That is enough to learn the builder and run a light personal workflow, and it is the right place to measure your real burn rate before paying for anything. [S6][S7]

Where Make fits against the alternatives

Make occupies the middle of the automation market on this site’s coverage: more visual and more forgiving than code-first tools, more powerful than simple task-based connectors, and priced per credit rather than per task or per execution. The trade against execution-based platforms is that Make’s meter is granular, so a ten-step scenario is not automatically cheaper than a two-step one. [S1][S5]

If self-hosting or execution-based billing matters, the n8n review and the n8n vs Make comparison cover that decision in detail, including the licensing differences. If you want the widest app catalog and the simplest billing, the Zapier review and the Zapier alternatives guide are the starting points. For self-hosted and code-first options, see the Activepieces review and the Pipedream review, and for a budget per-task alternative, the Pabbly Connect vs Zapier comparison.

Enterprise deployment and AI features

Enterprise pricing is quoted rather than published. The distinctive enterprise capability is the on-premise agent: an installed agent that lets Make scenarios reach systems on a private network without opening inbound firewall access, while orchestration still runs in Make’s cloud. Make’s documentation requires owner, admin, or app developer organization roles to create the agent, notes that the credentials are shown only once, and lists Java 11 or above as a prerequisite on the installer. For AI-heavy teams, custom AI provider connections became available on all paid plans in November 2025, which lets you bring your own OpenAI or Anthropic key and pay that vendor directly for tokens instead of consuming dynamic Make credits. [S3][S4]

Pros and cons

Pros

• Powerful visual builder for branching, multi-step workflows, with a free tier that is permanent rather than a trial. [S6][S7]
• Cheap entry pricing at the annual rate, and an official Help Center example confirming the $9 / 10,000-credit tier. [S2]
• Custom AI provider connections on every paid plan since November 2025, letting you avoid dynamic token credits. [S3]
• Extra credits keep scenarios running instead of hard-stopping at the limit, with published purchase rules. [S2]
• Higher tiers carry lower per-credit costs, and Pro reaches 8 million credits per month. [S2][S3]
• An on-premise agent for private-network access at enterprise scale. [S4]

Cons

• The credit model is harder to forecast than flat per-task billing, especially with AI features. [S6]
• Polling triggers and failed runs consume credits even when nothing useful happens. [S7]
• Extra credits cost 25 percent more than plan credits, and auto-purchasing can spend without a human in the loop. [S2][S3]
• Reported learning curve of roughly 5 to 10 hours before the canvas feels natural. [S7]
• Annual prepayment locks in capacity with no prorated refund if your needs change. [S6]
• Core’s execution priority queues during peak periods, which matters for customer-facing workflows. [S6]

Who should choose Make

Choose Make if you need branching logic, multiple steps, and a visual canvas that non-developers can maintain, and if you are willing to watch credit usage for the first month. It suits solo builders and small teams running scheduled or event-driven workflows, teams that want AI agents and custom AI provider keys, and organizations that need enterprise private-network connectivity. The annual rate makes the entry tier one of the cheaper ways into a serious automation platform. [S2][S5][S6][S7]

Who should look elsewhere

Skip Make if predictability is your primary requirement. High-volume workflows that lean on polling triggers, looping over large data sets, or Make’s own AI provider can consume credits far faster than the headline credit count suggests, and the 25 percent overage premium makes that expensive. If you would rather pay a flat rate for unlimited operations, a self-hosted option such as n8n changes the cost structure entirely, and if you want the simplest possible billing for linear automations, a task-priced tool is easier to budget. [S1][S2][S6][S7]

Buyer checklist

1. Start on the free plan and measure real credit burn for two weeks before upgrading. [S6]
2. Replace polling triggers with webhooks where the app supports them, and review failed runs. [S7]
3. Bring your own AI provider key if you use AI modules heavily, so token costs go to the vendor rather than into dynamic credits. [S1][S6]
4. Decide deliberately whether auto-purchasing should be on, and remember the 25 percent premium and the 10,000-credit purchase unit. [S2]
5. Model the credit ladder before prepaying annually, since there is no prorated refund. [S6]
6. Confirm current plan prices on the live pricing page. It was Cloudflare-protected during this review, so every dollar figure here is either an official Help Center example or a dated third-party reading. [S2][S5]

Final verdict

Make earns a conditional recommendation with medium confidence. The product is genuinely capable, the documentation around credits is unusually clear for a usage-based platform, and the entry pricing is competitive at the annual rate. The conditions are about budget discipline rather than product quality: credits disappear through polling, retries, and token-based AI, extra credits carry a 25 percent premium, and the official pricing page could not be read directly for this review. If you build on the free tier first and watch your burn rate, Make is one of the better values in visual automation. If you need a bill that never surprises you, choose a platform whose meter you can predict before you commit. [S1][S2][S5][S6][S7]