What leaders and teams rolling out Make report, with every finding tied to its evidence.
Read the findingsFrom 48 authors in 41 discussions. Run a pilot on one live workflow to measure failed runs and the time spent fixing them.
Jan 2025 to Sep 2026.
55 sources from practitioners, by month and sentiment.
Logic without code draws the most praise, and every source that discusses credits raises them as a concern. Fourteen sources build client scenarios, and 11 describe moving work off Make against 3 that stayed.
Positive, mixed and negative sources
The score counts them as 14 positive, 20 mixed and 14 negative votes, one per author. See How the numbers work.
See the evidenceBelow: 3 praise themes, 3 concerns, 1 point of agreement and 1 disagreement.
Counted for All users, from 55 sources. Change group
Every capability practitioners describe positively, ranked by how many sources say so. Open one to read who said it.
Counted for All users.
Positive, 8
Mixed
Ariel Moatti, developer with an IT specialist background (GitHub profile)
--blueprint requires inline JSON: Windows argv limit blocks writes of non-trivial scenariosGitHub issue on integromat/make-cli
Found the Make CLI useful in evaluation but unable to write 68 of 106 active production scenarios on Windows. Their blueprints exceed a 25KB argument limit, and the five largest run 240KB to 365KB.
Positive
Reddit user
Comment on: Alternative to Zapier? A few observationsReddit comment
Switched from Zapier to Make after hitting Dropbox API limits, took time to learn it, and would not go back.
Positive
Reddit user
Comment on: Is Make much worse than Zapier or I'm missing something? Alternatives?Reddit comment
Make is more customizable than Zapier and can do more, which is also why it has a bigger learning curve.
Positive
Founder of Scalevise, a development agency
How We Automated Project Administration with Jira, Make and AirtableCompany blog post, dev.to
The agency connects Jira worklogs to Airtable through Make scenarios for billing and project reporting, which it says saves each project manager 6 to 8 hours a week.
Positive
Automation builder, simplymation.eu
Comment on: Idea Farming for MakeReddit comment
An automation builder runs hundreds of production scenarios in Make, from client work to home heat pump controls.
Positive
Reddit user
3 automations that made my team think I hired an assistant (it's literally just Make workflows)Reddit post
Make workflows generate about 50 ad variations from one brief and run a Search Console to published-post content engine for the author's team; an outreach generator failed.
Positive
Make Community member
How we reduced 720K+ Operations Annually Using Make's Custom VariablesCommunity forum post
Cut 60,000 operations a month of repeated file lookups across 20 scenarios by storing monthly file IDs in custom variables updated by one scheduled scenario.
Positive
Reddit user
Comment on: Is Make much worse than Zapier or I'm missing something? Alternatives?Reddit comment
Spent early weeks troubleshooting Make, used ChatGPT on screenshots to learn how data passes between modules, and now automates far more than before.
Mixed or negative, 3
Mixed
Make Community member
Triggering scenario in the middle upon users approvalCommunity forum post
Could not pause a Make scenario mid-run for a user's approval, which n8n supports, and is weighing a switch for n8n's flexibility.
Mixed
Independent builder
Hands-Free AI Video: How I Connected Google Sheets and Luma via Make.comPersonal blog post, dev.to
Built a Google Sheets to Luma video pipeline in Make that saves real time, but needed a router workaround for optional API inputs and would compare n8n for heavier logic.
Negative
Hacker News commenter
Comment on: N8n - Flexible AI workflow automation for technical teamsHacker News comment
Switched from Make to n8n for local runs without limits and code nodes; building loops and error handling in Make's UI took 10 or more minutes per job.
Counted for All users.
Positive, 3
Mixed
Make power user of nearly 8 years who builds automations for clients
My perspective as new user from Make.comCommunity forum post
An eight-year Make power user says Make was far cheaper than Zapier but hard to learn, has since matched Zapier on apps, and is now trying self-hosted n8n.
Mixed
Wolfgang Wagner, TYPO3 trainer, integrator, and consultant
n8n always seemed too complicated to me. Until today.Personal blog post, wwagner.net
Ran 16 active Make scenarios and moved 14 to n8n in one day with Claude, because Make's bill grows with every workflow and operation. Wagner credits Make's ready-made modules for years of easy setup.
Negative
Hacker News commenter
Comment on: N8n - Flexible AI workflow automation for technical teamsHacker News comment
Switched from Make to n8n for local runs without limits and code nodes; building loops and error handling in Make's UI took 10 or more minutes per job.
Mixed or negative, 3
Mixed
Make Community member
Trying to use Make with Asana instead of Zapier - Why is there no Trigger on tasks moving to sections yet?Community forum post
Moving a Zapier flow to Make to use a non-US provider, found no Asana trigger for a task moving between sections and faced polling every minute instead.
Negative
Make Community member
Instagram - Create A Reel For Creator AccountsCommunity forum post
Make cannot post videos to TikTok or reels to an Instagram creator account, so posting goes through Zapier and Buffer while the user still pays for Make.
Mixed
Reddit user
Potentially moving over from Zapier and having difficulty with Squarespace integrationReddit post
Testing a move from Zapier, found Make's Squarespace modules cover only commerce, so a form-to-Kit flow needs workarounds that poll often and use more operations.
Counted for All users.
Positive, 1
Positive
Automation builder for clients
AI Agents FeedbackCommunity forum post
Is adding Make AI Agents to scenarios built earlier for clients and rates their potential highly.
Mixed or negative, 4
Negative
Make user scaling AI agents across scenarios
New AI-Agents: feedbackCommunity forum post
Prefers the old AI Agents: in the new version tools must be rebuilt for each agent, reasoning effort cannot be set, and agents cannot be named.
Mixed
Make Community member
Agents-MCP Server with Oauth2?Community forum post
Their team's self-hosted MCP server supports only OAuth2, which Make AI Agents could not connect to.
Mixed
Make Community member
Where are the AI agents?Community forum post
Loves Make but expected to switch to n8n unless Make shipped AI agents, even as a beta, because the feature had become essential.
Mixed
Solo builder
Introducing Credits: A New System Of BillingCommunity forum post
A solo builder worries that token-based billing for Make's AI features ends the predictable cost that kept a passion project running, though a personal OpenAI connection still costs 1 credit.
Every concern practitioners raise, most raised first.
Counted for All users.
Mixed
Wolfgang Wagner, TYPO3 trainer, integrator, and consultant
n8n always seemed too complicated to me. Until today.Personal blog post, wwagner.net
Ran 16 active Make scenarios and moved 14 to n8n in one day with Claude, because Make's bill grows with every workflow and operation. Wagner credits Make's ready-made modules for years of easy setup.
Negative
Make Community member
Reporting helpCommunity forum post
Asks for a per-scenario credit cap, because scenarios can use many credits and the cost only becomes clear once a scenario is built and run.
Mixed
Reddit user
Comment on: Tired of Zapier breaking at 2am. What does everyone actually trust for production?Reddit comment
Moved from Zapier to Make for its UI and lower price and found it easier to build and debug, then left for self-hosted n8n when the credit change raised costs 30%.
Mixed
New Make user handling client and account management
Asana usage running when there's no new activity?Community forum post
A new user found a polling Asana trigger set to every 3 minutes used credits all night with no activity, until a volunteer explained webhook triggers.
Negative
Automation freelancer
Anyone else getting killed by Make (integromat) operation costs ?Reddit post
After optimizing scenarios for five clients, still pays about US$150 a month in extra operations and is weighing self-hosted n8n for predictable cost.
Positive
Make Community member
How we reduced 720K+ Operations Annually Using Make's Custom VariablesCommunity forum post
Cut 60,000 operations a month of repeated file lookups across 20 scenarios by storing monthly file IDs in custom variables updated by one scheduled scenario.
Negative
Make user
Comment on: Introducing Credits: A New System Of BillingCommunity forum post
Objects that a Make trigger check uses a credit even when it finds nothing new, unlike Zapier.
Mixed
Make customer
Comment on: Introducing Credits: A New System Of BillingCommunity forum post
A credits display error blocked the team's runs on launch day; heavy use of Make AI modules raised their usage, which they still call reasonable, and support added credits.
Negative
Make Community member
Extra Credits Rest?Community forum post
Bought 10,000 extra credits just before the billing cycle reset and lost them two hours later when the cycle renewed.
Negative
Make user who manages two organizations
Comment on: Introducing Credits: A New System Of BillingCommunity forum post
Expects much higher credit use in the two organizations they manage, since a scenario that updates 10 spreadsheet rows uses 10 credits, and calls credits a hidden price rise.
Mixed
Solo builder
Introducing Credits: A New System Of BillingCommunity forum post
A solo builder worries that token-based billing for Make's AI features ends the predictable cost that kept a passion project running, though a personal OpenAI connection still costs 1 credit.
Mixed
Automation provider
Comment on: Anyone else getting killed by Make (integromat) operation costs ?Reddit comment
Weighs each scenario's monthly cost against what it saves, and moves high-cost flows from Make to Python on PythonAnywhere because clients will not support self-hosted n8n.
Mixed
Reddit user
Comment on: Anyone else getting killed by Make (integromat) operation costs ?Reddit comment
Moved the most operation-hungry scenarios to Microsoft Power Automate and rarely exceeds the Make operations limit now, while trialing n8n and Azure functions.
Mixed
Reddit user
Potentially moving over from Zapier and having difficulty with Squarespace integrationReddit post
Testing a move from Zapier, found Make's Squarespace modules cover only commerce, so a form-to-Kit flow needs workarounds that poll often and use more operations.
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.An operation is one module run, once per bundle it processes, and a trigger uses one each time it checks for data. For apps without AI, 1 operation is 1 credit; Make's AI Provider adds credits by input and output tokens. Credits
Open them in the recordCounted for All users.
Raised as a concern, 5
Negative
R Dilip Kumar, founder building VoiceLab (X profile)
I deleted the Make.com automation I built for thisX post
Deleted a Make scenario that created recurring Notion tasks after its modules and webhooks broke quietly. A scheduled Claude Code instruction reading one plain file now creates 17 tasks every Friday with no Make bill.
Mixed
Website operator
Comment on: White House website mysteriously streams personal finance YouTube creatorHacker News comment
A Make automation began publishing dozens of unrelated YouTube videos to a website when the YouTube API ignored its YouTube channel filter.
Negative
Make Community member
Service Outage: November 12thCommunity forum post
A Make user for over five years says recent outages lost webhook data for clients and that Make shared too little detail about the causes.
Negative
Make Community member
Instagram module suddenly failing with "Media ID is not available (9007, OAuthException)"Community forum post
Client workflows fail on Make's Instagram module while the same process runs cleanly in n8n; a five-attempt retry loop gets about 90% of posts through.
Mixed
Make customer
Comment on: Introducing Credits: A New System Of BillingCommunity forum post
A credits display error blocked the team's runs on launch day; heavy use of Make AI modules raised their usage, which they still call reasonable, and support added credits.
Discussed without concern, 2
Positive
Make Community member
Automation workflowsCommunity forum post
Manages many client scenarios by splitting them into small modules, using incomplete executions as retry queues visible on Make Grid, and raising custom errors on purpose.
Mixed
Make Community member
Is it possible to "transfer data"?Community forum post
A lead generation agency evaluating Make because Zapier became too expensive could not find an equivalent of Zapier's Transfer Data to resend missed leads.
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.With incomplete executions stored, Make retries runs that failed on rate limit, connection, or timeout errors on a backoff schedule. Error handlers such as Resume, Rollback, and Commit use no credits. Automatic retry of incomplete executions
Open them in the recordCounted for All users.
Raised as a concern, 4
Mixed
New Make user handling client and account management
Asana usage running when there's no new activity?Community forum post
A new user found a polling Asana trigger set to every 3 minutes used credits all night with no activity, until a volunteer explained webhook triggers.
Positive
Reddit user
Comment on: Is Make much worse than Zapier or I'm missing something? Alternatives?Reddit comment
Spent early weeks troubleshooting Make, used ChatGPT on screenshots to learn how data passes between modules, and now automates far more than before.
Negative
Rails developer
Comment on: How I build software quicklyHacker News comment
Gave up on prototyping an idea in Make and Google Sheets after two hours and built it as a Rails app in 30 minutes.
Mixed
Reddit user
Make.com AI Agent + Data Store: Key for GetRecordReddit post
Built a newsletter analyzer where a Make AI Agent orchestrates on-demand scenarios, but could not pass the Data Store record key between them.
Discussed without concern, 4
Positive
SEO content specialist
Everyone Starts With Zapier. Here's Why I Switched to Make.com Before Paying a CentPersonal blog post, dev.to
Left Zapier's free plan, which allows only two-step Zaps, for Make's free tier with multi-step scenarios, routers, and HTTP modules, accepting a harder learning curve.
Positive
Reddit user
Comment on: Alternative to Zapier? A few observationsReddit comment
Switched from Zapier to Make after hitting Dropbox API limits, took time to learn it, and would not go back.
Positive
Reddit user
Comment on: Is Make much worse than Zapier or I'm missing something? Alternatives?Reddit comment
Make is more customizable than Zapier and can do more, which is also why it has a bigger learning curve.
Mixed
Make power user of nearly 8 years who builds automations for clients
My perspective as new user from Make.comCommunity forum post
An eight-year Make power user says Make was far cheaper than Zapier but hard to learn, has since matched Zapier on apps, and is now trying self-hosted n8n.
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Scheduled scenarios run at most every 15 minutes on Free and as often as every minute on paid plans. Instant triggers start from webhooks. Make pricing
Open them in the recordStatements this group's sources agree on, then the ones close to agreement.
Freelancers, consultants, and agencies build Make scenarios for clients and choose it for mid-complexity delivery.
14 supporting sourcesClose to agreement: each needs 11 supporting sources
As logic, volume, or AI work grows, teams move workflows to n8n, code, or engineered APIs.
9 supporting sourcesTeams put LLM calls and agents inside routine work, moving data between apps and models or letting an assistant run scenarios through MCP.
7 supporting sourcesPeople pick Make over Zapier because the same work costs less: a more usable free plan and fewer billed units for multi-step workflows.
5 supporting sourcesQuestions the sources split on, with the count on each side.
Evidence remains mixed
Stay on Make, 3 sources
Some keep Make or choose it over Zapier for its logic, free plan, and code they avoid writing.
Move workflows off, 11 sources
Others move workflows to n8n, code, or a dedicated tool when loops, upkeep, or silent failures cost too much.
The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.
Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on All users. Leaders and teams have 19 accounts; GILD prints their sentiment from 20.
25 sources. These accounts weigh cost at volume, client delivery, and what breaks, as small teams, agencies, and departments report them.
30 sources. These accounts weigh the logic Make can express against what it costs and how long it takes to learn, as individual users report them.
55 sources. This broad read combines individual automations with agency and team use that reach different conclusions.
55 sources from practitioners, by the context they work in. Filled rows count for this group.
Emphasizes Credits, client work, and moves to n8n or code
Emphasizes Agency delivery for clients, credit bills, and outages
Emphasizes Routine team work and AI steps built without code
Emphasizes IT and transformation leaders: use the named customer rollouts and Operator Insights as reference points
Emphasizes ChargeGuru, FranklinCovey, and Stellantis &You UK rollouts, from dated Make case studies, shown as Operator Insights
What changes with scale. Individual users write most about credit costs and about leaving Make for n8n or custom code. Small teams and agencies run scenarios for clients, where credit bills and outages land on them. Named department and company accounts lean positive, describing AI steps inside routine work and scenarios heavy with business logic.
Where this group's sources were published.
Counted for All users, from 55 sources. Change group
72 sources for this group, 17 of them documentation
Older evidence stays when it still applies. Records based on replaced features stay in the history with the Needs a recheck label.
See sources by originWho each source is, how it knows, whether it still applies and what it counts toward.
Newest first, on its own page. Every count above opens its sources there.
Read all 72 sourcesAbout this read
A running review of what people using Make at work report, from individual users to company-wide rollouts. Each finding links to its sources, and each conflict shows both sides.
Counts cover only the sources GILD reviewed.
Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.
A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.
Flagged for a recheck, of the sources that take a side: leaders and teams 0 of 19, individual users 1 of 30, all users 1 of 49.
Each row opens its sources for the group you are reading.
| Finding | Leaders and teams rolling it out | Individual users | All users | Sources |
|---|---|---|---|---|
| Current readCurrent sentiment | 6 positive, 7 mixed, 6 negative | 9 positive, 13 mixed, 8 negative | 15 positive, 20 mixed, 14 negative | Sources |
| PraiseLogic without code | 5 of 5 positive | 3 of 6 positive | 8 of 11 positive | Sources |
| PraiseApp coverage | 0 of 0 positive (under the minimum) | 3 of 6 positive | 3 of 6 positive | Sources |
| PraiseAI agents & MCP | 0 of 1 positive (under the minimum) | 1 of 4 positive (under the minimum) | 1 of 5 positive | Sources |
| ConcernCredit metering | 6 of 6 raise it | 8 of 8 raise it | 14 of 14 raise it | Sources |
| ConcernLearning curve | 1 of 2 raise it (under the minimum) | 3 of 6 raise it | 4 of 8 raise it | Sources |
| ConcernRun failures | 4 of 6 raise it | 1 of 1 raise it (under the minimum) | 5 of 7 raise it | Sources |
| ConsensusMake carries the AI steps | 2 supporting (under the minimum) | 5 supporting (below threshold) | 7 supporting (below threshold) | Sources |
| ConsensusBuilt for clients | 8 supporting | 6 supporting | 14 supporting | Sources |
| ConsensusChosen over Zapier on cost | 1 supporting (under the minimum) | 4 supporting (under the minimum) | 5 supporting (below threshold) | Sources |
| ConsensusHeavy work moves to code | 3 supporting (under the minimum) | 6 supporting | 9 supporting (below threshold) | Sources |
| DisagreementShould a team keep its automations on Make or move them to n8n or code? | Stay on Make 2, Move workflows off 3 | Stay on Make 1, Move workflows off 8 (under the minimum) | Stay on Make 3, Move workflows off 11 | Sources |
| Current readEvidence mix | 42 sources | 47 sources | 72 sources | Sources |
GILD's checks of claims against official documentation, kept apart from the source counts.
