Make

Make Problems & Issues

Saas

Visual no-code automation platform (formerly Integromat)

Overall Score62/100
Pricing
66
Usability
62
Performance
60
Support
40
Reliability
55
Onboarding
50
Integrations
85

Much cheaper than Zapier for multi-step automations and very capable visually, but credit consumption from polling and loops surprises users, webhooks and OAuth connections fail silently, scenarios auto-disable after errors or outages, and support is ticket-only and slow on billing disputes.

Should you use Make?

Try with caution

Make works for some teams, but users report recurring problems (score 62/100). Most reported issues: Why does Make use so many credits?; Make webhook not triggering the scenario; Make scenarios turn off automatically after errors. Not a good fit for: Developers wanting code and self-hosting; Teams needing strict data residency on their own servers. Users most often switch to Zapier, n8n, Pipedream.

Top problems

  • Why does Make use so many credits?
  • Make webhook not triggering the scenario
  • Make scenarios turn off automatically after errors

Good for

  • Automation agencies and freelancers
  • Ops and marketing teams with multi-step workflows
  • Small businesses moving off Zapier to save money

Avoid if you are

  • Developers wanting code and self-hosting
  • Teams needing strict data residency on their own servers

Common alternatives: Zapier, n8n, Pipedream

Overview

Make (make.com, formerly Integromat) is a visual automation platform where you build 'scenarios' that connect apps, APIs and AI models with routers, iterators, aggregators and error handlers on a drag-and-drop canvas. It bills per credit (formerly operations): most module actions cost 1 credit, including every polling check. It sits between Zapier (simpler, pricier) and n8n (more technical, self-hostable) and is popular with agencies, ops teams and freelancers.

13 signals analyzed
45 sources reviewed
Last analyzed: Oct 2026
Company Info
Company:Make (Celonis)
Founded:2012
HQ:Prague, Czech Republic
Website:www.make.com

Make Not Working? Common Errors & Fixes

Step-by-step fixes for the errors users hit most.

Signals & Issues

Patterns extracted from real user feedback — not raw reviews.

Pricing3 signals
Why does Make use so many credits?

Every module action costs a credit, and polling triggers (Watch modules) spend a credit on every check even when nothing new is found. A trigger polling every minute burns roughly 44,000 credits a month on its own, and loops through iterators multiply usage per bundle.

Impact: 8/10Reported 9xNegativevia Other (4 sources)hidden costs
Make switched from operations to credits (AI modules cost more)

On August 27, 2025 Make replaced operations with credits as its billing unit. Standard actions still cost 1 credit, but features using Make's built-in AI provider are billed by actual usage and can consume several credits per run, so AI-heavy scenarios got more expensive.

Impact: 6/10Reported 7xNegativevia Other (3 sources)price increase
Make extra credits now cost 25% more, Core capped at 300k credits

From November 6, 2025 extra credits cost 25% more than plan credits whether bought manually (previously no premium) or via auto-purchase (previously 30%). Core was capped at 300,000 credits per month, pushing heavier users to Pro.

Impact: 6/10Reported 6xNegativevia Other (2 sources)price increase
Reliability3 signals
Make webhook not triggering the scenario

One of the most common community threads: webhooks that only fire on 'Run once', stop working after weeks, or never receive data from the sender. Causes range from the scenario being off or scheduled instead of instant, to wrong data structure, to webhooks auto-deactivated after 5 days unused.

Impact: 8/10Reported 8xNegativevia Other (5 sources)workflow failure
Make scenarios turn off automatically after errors

Make disables a scenario's schedule after several consecutive errors and immediately on fatal errors like data size limits. This protects credits but means automations silently stop until someone notices and re-enables them.

Impact: 8/10Reported 7xNegativevia Other (3 sources)workflow failure
Make outages disabled scenarios and dropped webhooks

Incidents in Sept 2025 (all scenarios, ~2 hours), Dec 2025 (Cloudflare), March 2026 (US2 webhooks), July 2026 (~250 scenarios disabled for about 29 hours) and Oct 2026 (Scenario app failures) left automations stopped or webhooks unprocessed, often requiring manual re-enabling.

Impact: 8/10Reported 5xNegativevia Other (4 sources)workflow failure
Integrations1 signal
Make connections keep expiring (invalid refresh token)

Gmail, Google Drive and Microsoft 365 connections regularly fail with 'invalid_grant' or 'Invalid refresh token, please reauthorize'. Some users hit it weekly because their Google Cloud app is in testing mode, and in some threads reauthorizing doesn't fix it.

Impact: 7/10Reported 7xNegativevia Other (5 sources)workflow failure
Support1 signal
Make support is slow and billing refunds are hard

Trustpilot reviewers describe weeks without replies and refunds only after pushing, including a case of credits charged multiple times due to platform lag. Community users note the support ticket form is the only direct contact channel.

Impact: 7/10Reported 6xNegativevia Trustpilot (3 sources)support breakdown
Onboarding1 signal
Make has a steep learning curve (bundles, iterators, aggregators)

Reviewers consistently say Make takes days to weeks before building complex scenarios comfortably. Concepts like bundles, iterators, aggregators, mapping and filters confuse non-technical users who expected Zapier-level simplicity.

Impact: 5/10Reported 8xNegativevia Capterra (4 sources)expectation mismatch
Usability1 signal
Make errors are hard to diagnose

Capterra reviewers report that errors are hard to trace and fix, and community threads show generic messages like BundleValidationError usually point to an empty value from an upstream module rather than the module that failed.

Impact: 6/10Reported 6xNegativevia Capterra (3 sources)workflow failure
Performance3 signals
Make scenarios time out after 40 minutes

Paid plans stop a run after 40 minutes (5 minutes on Free) with ExecutionInterruptedError, leaving remaining bundles unprocessed. Large syncs must be split into chained scenarios or batched.

Impact: 6/10Reported 5xNegativevia Other (3 sources)scaling breaks
Make hits rate limits (429) on busy scenarios

Instant triggers and bulk processing frequently hit third-party API limits (Webflow, Google Drive), and the app's limit is shared across all your scenarios. Make itself also caps incoming webhooks at 300 requests per 10 seconds.

Impact: 5/10Reported 5xNegativevia Other (4 sources)scaling breaks
Make editor is slow with large scenarios

Reviewers mention UI sluggishness, lag and occasional freezes when scenarios grow to many modules.

Impact: 4/10Reported 4xNegativevia Trustpilot (2 sources)

What Users Love

Far cheaper than Zapier for multi-step workflows

10,000 credits start at $9/month (annual), which buys much more automation than an equivalent Zapier plan for multi-step scenarios.

PricingMentioned 8x4 sources

Powerful visual scenario builder

Routers, iterators, aggregators and filters on a visual canvas handle branching and bulk data that linear tools can't.

UsabilityMentioned 8x4 sources

Large app library plus HTTP module

Thousands of prebuilt app modules and a generic HTTP/webhook module cover almost any API without code.

IntegrationsMentioned 7x3 sources

Built-in error handlers that don't cost credits

Error handler routes (Resume, Skip, Break, Rollback) and routers don't consume credits, and incomplete executions can be stored and retried.

ReliabilityMentioned 5x2 sources

Usable free plan for testing

The Free plan includes 1,000 credits a month and 2 active scenarios, enough to learn the tool and run light automations.

PricingMentioned 5x2 sources

Pricing Plans

Free
$0/mo

Storage: 1 MB data storage

  • ✓1,000 credits/month
  • ✓2 active scenarios
  • ✓15-minute minimum interval
  • ✓1 data store

Limitations: 5-minute max execution time, 5 MB file size, 7-day log retention.

Core
$10.59/mo
  • ✓10,000 credits/month (scalable up to 300,000)
  • ✓Unlimited active scenarios
  • ✓1-minute minimum interval
  • ✓40-minute max execution time

Limitations: $9/month billed annually ($108/year). 100 MB file size, 30-day logs. Unused credits expire at end of term.

Extra credits cost 25% more than plan credits; auto-purchase buys 10,000-credit packs when you run out; polling triggers use credits on every check.
Pro
Popular
$18.82/mo
  • ✓10,000 credits/month (scalable up to 8M)
  • ✓Priority execution
  • ✓Full-text execution log search
  • ✓250 MB file size

Limitations: $16/month billed annually ($192/year).

Extra credits cost 25% more than plan credits; AI-provider modules can use more than 1 credit per run.
Teams
$34.12/mo
  • ✓10,000 credits/month (scalable)
  • ✓Team roles and permissions
  • ✓Shared scenario templates
  • ✓500 MB file size

Limitations: $29/month billed annually ($348/year).

Extra credits cost 25% more than plan credits.
Enterprise
Free
  • ✓Custom credits
  • ✓60-day log retention
  • ✓1,000 MB file size
  • ✓Invoice / wire transfer payment

Limitations: Custom pricing via sales.

Features

Automation

  • Visual scenario builder

    Routers, iterators, aggregators, filters

Triggers

  • Instant webhooks

    Queue size scales with plan credits (667 per 10k, max 10,000)

Reliability

  • Error handlers

    Resume, Skip, Break, Rollback, Commit; don't consume credits

  • Incomplete executions storage

AI

  • Custom AI provider connections

    All paid plans since Nov 2025

Deployment

  • Self-hosting

    Cloud only

Developer

  • Custom code in modules

    Limited compared with n8n Code nodes

Who Should Use This?

Good Fit

Automation agencies and freelancers

Visual builder and low per-credit cost suit building many client workflows.

Ops and marketing teams with multi-step workflows

Branching and bulk processing are much cheaper than on Zapier.

Small businesses moving off Zapier to save money

Same integrations for a fraction of the price, if someone can learn the builder.

Neutral

Complete beginners wanting simple two-step zaps

Works, but Zapier is easier to learn for simple triggers and actions.

High-volume polling workloads

Every check costs a credit; switch to webhooks or costs climb quickly.

Avoid

Developers wanting code and self-hosting

No self-hosting and limited custom code; n8n fits better.

Teams needing strict data residency on their own servers

Make is cloud-only.

Regret Patterns

Common buyer's remorse scenarios reported by users.

Credits gone in days because of polling triggers

Users set Watch triggers to every minute or every few minutes and burn most of the monthly allowance on empty checks.

First billing cycle
Reported 8x
Automations silently stopped after auto-disable

A scenario hit consecutive errors or an outage, Make turned it off, and nobody noticed for days.

First few months
Reported 6x
Expected Zapier-simple, got a learning curve

Beginners switch for price, then struggle with bundles, iterators, aggregators and data mapping.

First week
Reported 6x
Connections keep needing reauthorization

Google and Microsoft connections expire with refresh-token errors, breaking scenarios until reconnected.

Weeks after setup
Reported 6x
Billing disputes with slow support

Users charged extra credits by lag or auto-purchase report long waits and resistance to refunds.

After an unexpected charge
Reported 4x
AI scenarios cost more after the credits switch

Scenarios using Make's AI provider consume variable credits, making costs less predictable than flat operations.

After August 2025
Reported 4x

When It Breaks Down

Scenarios where this product tends to fail users.

High-frequency polling triggers
pricing

Each check costs a credit; a 1-minute poll uses ~44,000 credits a month before doing any work.

Large data syncs over 40 minutes
performance

Runs end with ExecutionInterruptedError and leftover bundles are not processed.

Burst webhook traffic
reliability

More than 300 requests per 10 seconds return 429, and full queues reject data with 'Queue is full'.

Many scenarios hitting the same API
integrations

Rate limits are shared across scenarios, so 429 RateLimitError appears under load.

Google apps in OAuth testing mode
integrations

Refresh tokens expire about weekly, so connections fail with 'invalid refresh token'.

Platform outages
reliability

Webhooks received during incidents may not be processed and scenarios may be auto-disabled.

Alternatives Users Switch To

Zapier

9x mentioned

Easiest automation tool with the largest app library and better beginner onboarding; trade-off is a much higher price per task, especially for multi-step workflows.

n8n

9x mentioned

Self-host for free with unlimited executions, bills per workflow run in the cloud and allows JavaScript/Python code; trade-off is a steeper learning curve and server maintenance.

Pipedream

5x mentioned

Developer-first automation with code steps in Node.js/Python; better for API-heavy work, worse for non-coders.

Microsoft Power Automate

5x mentioned

Included with many Microsoft 365 plans and strong for Microsoft-centric workflows; clunkier outside the Microsoft ecosystem.

Activepieces

4x mentioned

Open-source, self-hostable no-code builder with a simpler UI; smaller integration library.

IFTTT

3x mentioned

Very simple consumer automations at low cost; not suitable for business workflows with branching or data processing.

Frequently Asked Questions

See how Make compares in our Best Automation Software rankings, or calculate costs with our Budget Calculator.

Work at Make or spotted something outdated? Suggest a correction — we verify every change against public sources. See our methodology.