Make Reviews: 4.7/5 — Highly Rated

Make gives you 5 GB of monthly data transfer on its $9 Core plan. On the $16 Pro plan it is 5 GB. On the $29 Teams plan it is 5 GB. On Enterprise it is 5 GB. Maximum file size climbs steadily across those tiers — 100 MB, 250 MB, 500 MB, 1000 MB — which reads as though throughput is scaling with price. It is not. If your automations move a lot of data rather than a few large files, the cheapest paid plan gives you exactly as much room as the most expensive one.

• What it is: A visual, no-code automation platform in the iPaaS category, connecting 3,000-plus apps.
• Best for: Teams building multi-step workflows visually rather than writing integration code.
• Pricing: Free; Core $9, Pro $16, Teams $29 per month at 10,000 credits; Enterprise quoted. Verified July 2026.
• The honest catch: The free plan enforces a 15-minute minimum interval between runs.

What Is Make?

Make — formerly Integromat — is a visual automation platform. You build scenarios by dragging modules onto a canvas and wiring them together, with routers, filters, and error handling, across more than 3,000 connected apps. It is the more visual and more powerful end of the no-code automation market, sitting between Zapier’s simplicity and a developer-grade integration platform.

The meter is credits. Make’s own FAQ defines them plainly: “Every time a module in a scenario performs an action, it consumes credits. For example, when your scenario reads a record from Pipedrive, writes a row into a Google Sheet, or posts a tweet, each counts as one credit.” Most actions cost one, but the page notes that “some advanced features leveraging Make’s AI Provider may use more” — so AI-heavy scenarios burn the allowance faster than the count of steps suggests.

All three published plans start at the 10,000-credit level and scale upward through a selector running 20k, 40k, 80k, 150k, 300k, 500k, 750k, 1M and beyond, to 8M and above.

How Make Works

• Credits are the primary meter, from 1,000 free to 8M-plus.
• Prices quoted are at 10,000 credits — the selector raises them from there.
• Data transfer is flat at 5 GB on every paid tier.
• The free plan throttles frequency, not just volume.
• Annual billing saves “15% or more.”
• AI actions can consume more than one credit each.

Make Pricing

Captured from Make’s pricing page in July 2026 in US dollars, at the 10,000-credit level.

What actually decides your plan:

• Data transfer does not scale with price. Every paid tier from $9 to Enterprise allows 5 GB a month. What does scale is the maximum size of a single file — 100 MB, 250 MB, 500 MB, 1000 MB. Those are different constraints, and only one of them is a throughput limit. A workflow syncing thousands of small records hits the same ceiling on Teams as on Core.
• The free plan’s real limit is the clock, not the credits. A 15-minute minimum interval between runs means nothing on the free tier can respond promptly to anything. Combined with two active scenarios, it is a demonstration environment rather than a working one. Per-minute scheduling is the single biggest thing $9 buys.
• Core at $9 is a genuinely complete plan. Unlimited active scenarios, scheduling down to the minute, API access, 100 MB files, and 30-day logs. Most of what people upgrade for is not capacity but collaboration.
• Pro buys speed and searchability. Priority scenario execution, custom variables, and full-text execution log search for $7 more. If you are debugging complex scenarios regularly, full-text log search alone can justify it; if you are not, it will not.
• Teams is a per-organisation feature, not a per-seat one. Team roles and shared scenario templates at $29 is the plan for more than one builder. Note that it does not raise your data transfer or your log retention.
• Credits are what you actually budget. The published $9, $16, and $29 are the entry configuration at 10,000 credits. Model your monthly action count first, then read the price at that step, because the selector is what moves the bill.

Who Should Use Make

• Teams building genuinely complex workflows. The clearest case — routers, filters, and error handling make Make substantially more capable than simpler tools.
• Anyone automating across many apps. More than 3,000 integrations, with a visual canvas that keeps multi-branch logic legible.
• Budget-conscious automators. At $9 for unlimited scenarios and per-minute scheduling, Core undercuts most of the category.
• Operations teams standardising a process. Shared templates and team roles on the $29 Teams plan.

It fits poorly for high-volume data movement, where the flat 5 GB ceiling applies at every price; for teams wanting the simplest possible tool, where the visual canvas is more than they need; and for organisations requiring self-hosting, which Make does not offer.

Honest Pros and Cons

Strengths

• $9 for unlimited active scenarios and per-minute scheduling.
• 3,000-plus app integrations on every tier including free.
• A genuinely powerful visual builder with routers, filters, and branching.
• A permanent free plan with no time limit.
• A clear, published definition of what a credit is.
• Annual billing saves 15% or more.

Limitations

• Data transfer is 5 GB on every paid plan, from $9 to Enterprise.
• The free plan enforces a 15-minute minimum interval.
• Only two active scenarios on free.
• Log retention stays at 30 days through Teams.
• AI-powered actions consume more than one credit each.
• The published prices describe only the 10,000-credit step.

Make Alternatives and How It Compares

• n8n is the closest technical competitor and can be self-hosted, which Make cannot.
• Zapier is simpler and better known, with a larger app catalogue and higher prices.
• Workato and Tray.ai target enterprise integration with quoted pricing.
• Pabbly Connect and Activepieces compete at the budget end.
• Power Automate is the natural choice inside a Microsoft estate.

For a broader survey, browse our iPaaS directory.

The Verdict

Make is the best-value serious automation platform in this category, and the reason is Core. At $9 a month you get unlimited active scenarios, scheduling down to the minute, API access, and the full visual builder with routers, filters, and branching. Competitors charge multiples of that for less capability, and the free plan — permanent, with 1,000 credits and 3,000-plus integrations — is a real way to evaluate it rather than a countdown.

One number does not do what its neighbours imply. The monthly data transfer allowance is 5 GB on Core, 5 GB on Pro, 5 GB on Teams, and 5 GB on Enterprise. Sitting right beside it, maximum file size climbs from 100 MB to 1000 MB across the same tiers, which makes the whole block read like a capacity ladder. It is not one. Single-file size and total monthly throughput are different limits, and only the first improves as you pay. If your scenarios move large volumes of small records — a nightly sync, a high-traffic webhook, a data warehouse feed — upgrading from Core to Teams buys you collaboration features and precisely no additional headroom.

Two smaller things worth pricing in. The free plan’s binding constraint is the 15-minute minimum interval between runs, not the credit allowance — nothing on it can react promptly, which makes it unsuitable for anything user-facing regardless of volume. And the published $9, $16, and $29 describe the 10,000-credit configuration only; the selector runs to eight million and beyond, so estimate your monthly action count before treating any of those figures as your price. Make deserves credit for defining a credit unambiguously in its own FAQ, which is more than several competitors manage.

FAQ

How much does Make cost?

Captured in July 2026 in US dollars at the 10,000-credit level: Free at $0 with up to 1,000 credits a month, Core at $9, Pro at $16, and Teams at $29 per month, with Enterprise quoted. All paid plans use a credit selector running from 10,000 up past eight million, and the price rises with it. Annual billing saves “15% or more” according to the page.

What is a credit in Make?

An action performed by a module. Make’s FAQ states: “Every time a module in a scenario performs an action, it consumes credits. For example, when your scenario reads a record from Pipedrive, writes a row into a Google Sheet, or posts a tweet, each counts as one credit.” Most actions cost one credit, but the page notes that some advanced features using Make’s AI Provider consume more.

Does a more expensive Make plan give more data transfer?

No. The monthly data transfer allowance is 512 MB on Free and then a flat 5 GB on Core, Pro, Teams, and Enterprise alike. What does increase across those tiers is the maximum size of an individual file — 100 MB, 250 MB, 500 MB, and 1000 MB respectively. Those are separate limits, and only the file-size one scales with price.

What are the limits on Make’s free plan?

Up to 1,000 credits per month, a maximum of two active scenarios, a 15-minute minimum interval between runs, 512 MB of data transfer, 5 MB maximum file size, and 7 days of execution log storage. It has no time limit. In practice the 15-minute interval is the constraint that matters most, since it rules out anything that needs to respond promptly.

Make or n8n?

Both are powerful visual automation tools at similar price points, and the deciding factor is usually hosting. n8n can be self-hosted, which matters for teams with data residency or compliance requirements, and it appeals more to technical users. Make is fully managed, has a more polished builder, and a larger catalogue of ready-made integrations. Choose n8n for control, Make for convenience.