Make Pricing 2026

Make.com (formerly Integromat) is a visual workflow automation platform that connects 3,000+ apps and services without code. It uses a credit-based pricing model: each module execution counts as one operation, and by default one operation costs one credit. Make excels at complex multi-step workflows with visual mapping, conditional logic, and data transformation. It competes with Zapier, n8n, and Activepieces in the automation space.

Operations in Make.com are individual module executions within a scenario. Each step (like fetching a Google Sheet row, sending a Slack message, or updating an Airtable record) counts as 1 operation. A scenario with 5 steps that runs 100 times consumes 500 operations. Loops and iterations multiply operation counts. Make bills in credits, and by default 1 operation costs 1 credit. Trigger modules that check for new data use one operation per check, even when nothing new is found. Understanding operation consumption is critical to choosing the right plan.

Make.com uses a credit-based system where 1 credit = 1 operation (module execution). Free plan includes 1,000 credits/month; Core includes 10,000. Make's pricing page says credits expire at the end of the term, and extra credits bought on a monthly subscription expire after one month, so don't plan on carrying unused credits forward. Purchasing additional credits costs 25% more (auto or manual). Monitor your scenario complexity to estimate monthly credit consumption and avoid overages.

Yes, Make.com allows upgrades and downgrades between plans (Free, Core, Pro, Teams, Enterprise) at any time. Downgrades take effect at the next billing cycle. Upgrades are immediate. Changing plans frequently is supported, making Make flexible for seasonal workloads.

Make's permanent Free plan (1,000 credits/month) is the main way to try it, but it is not full feature access. Users report the Free plan is capped at 2 active scenarios (unlimited active scenarios start on Core), premium modules are locked, and scenarios can run no more often than every 15 minutes. Users also describe a free premium trial during which premium modules are available; those modules lock when the trial ends, breaking any scenario built on them.

Make bills in credits. Each module run in a scenario is an operation, and by default one operation costs one credit. The Free plan includes 1,000 credits/month, Core includes 10,000 credits/month, and higher tiers scale up. Complex workflows with iterations can consume credits quickly—for example, processing 3,000 emails with 3 steps each = 9,000 operations, or 9,000 credits.

Yes. Every scenario execution, including test runs during development, consumes credits from your monthly quota. Users report running out of credits while learning the platform, forcing mid-month upgrades to continue building.

Premium modules used during the free trial become locked once the trial expires. You cannot run scenarios using these modules without upgrading to a paid plan, even if you've already built the entire workflow. Make does not warn users during setup which modules are premium.

No. Make's policy explicitly states no refunds are offered, even if you cancel shortly after subscribing. Multiple users report being denied refunds after requesting them within 30 days.

Yes. Upgrading or downgrading your subscription triggers a new charge, regardless of where you are in your billing cycle. Users report being billed every time they modify their plan tier.

Yes. Make's Free plan is a permanent free tier that includes 1,000 credits per month, basic modules and integrations, and the visual scenario builder. Users report it is capped at 2 active scenarios (the limit shown in Make's app); unlimited active scenarios start on Core. Testing, debugging, and every check a scheduled trigger makes also consume credits, so the effective production capacity is lower than 1,000 credits. Premium modules are locked on the Free plan.

Any workflow that uses premium-tier modules will stop functioning when the trial ends unless you upgrade to a paid plan that includes access to those modules. Make does not warn you during the build process that specific modules are premium-only. Multiple users report discovering this only after investing days of build time.

Based on multiple user reviews, Make does not offer readily accessible live support. Reviewers report no phone or live chat option, and describe being directed to an outdated wiki or told to hire a freelancer when submitting a support ticket. The primary human contact path appears to be the sales team, not technical or billing support.

Make's cancellation flow requires completing multiple confirmation screens, including partially hidden checkboxes and repeated consent prompts. Several users report believing they had cancelled but continuing to be billed because they did not complete every step. After cancelling, verify your account reflects the Free plan before your next billing date.

Satisfied users cite Make's cost-effectiveness and workflow flexibility as advantages over Zapier. However, multiple users who switched away from Make cite n8n's self-hosted option as a free alternative for teams with technical resources. The decision typically turns on whether your team can tolerate Make's interface complexity and limited support in exchange for lower cost relative to Zapier.

Make has a significant learning curve for complex automations. Multiple Trustpilot reviewers report spending days or weeks on a single scenario. G2 reviewers note the visual diagram-based interface is intuitive once you learn it, and Make provides a course library for self-guided learning. Basic workflows are accessible to non-coders; complex multi-step scenarios involving filters, iterators, cursors, and API modules are where most users report struggling.

Multiple users report that Make's standard support is limited to documentation, wikis, and community forums, with no direct human agent access. One Trustpilot reviewer noted that when their account was hacked and incurred several thousand dollars in charges, they were directed only to an outdated wiki. Another reviewer described customer service as 'basically IMPOSSIBLE to contact.' Human support appears to be available primarily to sales prospects or Enterprise plan holders.

No confirmed nonprofit, startup, or education discount programs were found in available sources. Make's published pricing does not show an additional discount for annual billing versus monthly billing based on current tier data.

Make allows cancellation, but multiple users report the cancellation flow is intentionally difficult — requiring several confirmation screens and checkboxes that are easy to overlook. Users have reported being charged for additional months after believing they had fully cancelled. To avoid unexpected charges: complete every confirmation step in sequence, and look for a final confirmation that your account has been placed on the Free tier. Screenshot the confirmation screen as evidence.

Any scenarios built using premium-tier modules will stop executing immediately upon downgrade to Free — those modules become inaccessible. You'll need to rebuild those workflows using only the modules available on the Free tier, or remain on a paid plan. The Free plan's 1,000 credits/month and its reported cap of 2 active scenarios also apply immediately upon downgrade.

Multiple users report that Make does not provide accessible human support for non-sales inquiries — support contacts redirect to a wiki or community forum. One user reported an account security breach resulting in thousands of dollars in unauthorized charges, with no pathway to reach a human outside the sales team. Enterprise plan customers may have access to dedicated account support, but this is not confirmed in available sources.

Make's Free plan includes 1,000 credits per month, which works for very simple, stable automations. However, testing and debugging count against this quota — not just production runs — and a scheduled trigger spends a credit on every check: polling every 15 minutes uses about 2,880 credits in 30 days. Users also report a cap of 2 active scenarios. Users building or iterating complex workflows often exhaust the free limit during the build phase alone, making an upgrade necessary sooner than expected.

Yes — multiple users report the cancellation flow is deliberately complex, involving several sequential confirmation screens with barely visible checkboxes. At least one reviewer believed they had canceled but had not completed the final step, resulting in continued billing. Budget extra time before your renewal date and verify the cancellation confirmation email.

Customer support is a frequently cited pain point. Multiple reviewers report that it is very difficult to reach a human — the primary contact path appears to be sales, not technical support. Users with urgent billing or account issues (including a reported account compromise that resulted in thousands of dollars in charges) were directed to an outdated wiki rather than a live support agent.

Workflows built using premium modules (for example, during a free trial period) will break if your account reverts to or remains on the Free plan, since those modules are locked at that tier. Any automation relying on a premium integration will stop functioning until you upgrade to a plan that includes those modules.

Yes. Testing and debugging consume the same credits as live production runs. On the Free plan, this means you can exhaust all 1,000 monthly credits before a single automation goes into production — particularly for complex multi-step scenarios that require many test iterations.

Multiple user reviews report that Make's platform introduces bugs and breaks existing scenarios when releasing new features. Users have reported needing to rebuild scenarios after platform updates, which creates an ongoing maintenance burden not reflected in the subscription cost.