Key findings
- All 14 accounts that discuss credit metering raise it as a concern. They report trigger checks that find nothing new and an agency paying about US$150 a month in extra credits for five clients.
- 11 of 14 accounts discussing routers, iterators, and data handling are positive. The other 3 hit limits with loops, approvals, or optional inputs.
- Client delivery is the use most accounts share. 14 come from freelancers or agencies running Make scenarios for clients.
- Run failures are the next concern after credits. Of 9 accounts discussing failures, 7 report outages, silent breaks, or a module that fails on one post in ten.
- Sentiment is even. Score is 0 overall, and 0 among both the 20 team accounts and the 31 individual users.
Make suits teams that want routing and data-handling logic without code and will watch credit use closely. Across these public accounts, published between January 2025 and September 2026, that logic draws the most praise and credit metering the most concern. Twelve accounts describe moving work off Make, against 3 that chose it or stayed.
Where the value shows up
Builders credit Make with logic they would otherwise write as code. One left Zapier after hitting Dropbox API limits and would not return. A team saved 60,000 monthly operations by caching file IDs in custom variables. An agency reports saving each project manager hours a week with Jira-to-Airtable scenarios. Five accounts chose Make over Zapier on cost. One consultant counts 30 to 60% fewer billed units for the same workflows.
Fourteen accounts build client scenarios. They include a freelancer who learned from YouTube tutorials and an agency that monitors workflows across clients.
Where people hit limits
Users complain about polling through idle hours and extra credits expiring at monthly reset. One builder's usage rose 30% when the August 2025 credit change began charging for previously free modules. Another asks for per-scenario credit caps.
An agency with five years on Make lost webhook data during regional outages. One builder succeeds with about 90% of Instagram posts after a five-attempt retry loop. A competitive intelligence analyst replaced about 15 GPT scenarios after silent failures.
Why some move, and why some stay
Twelve accounts moved work, or plan to move it, to n8n, AWS Lambda, Power Automate, a Rails app, a dedicated tool, or a scheduled AI agent. Cost at volume is the main reason. One rebuilt a 120-module scenario as 6 n8n nodes, and a TYPO3 consultant moved 14 of 16 scenarios to n8n in one day with Claude. Three chose Make or stayed. One left Zapier over API limits. A content specialist wanted free multi-step scenarios, and an agency owner refuses to migrate client workflows.
AI and agents
Eight accounts put AI steps in Make. Uses include ChatGPT payment reminders and about 50 ad variations from one marketing brief. Four of 5 accounts discussing Make's own agent features are critical. One waited in March 2025 for a release date. Others report lost tool sharing or failed OAuth2 MCP connections, or object to token-based billing.
What an engineering leader set up
Perk, the travel and spend company with more than 1,800 employees, rolled Make out so non-technical departments could build their own automations without pulling engineers off the product. Gabriel Stock, a senior engineering manager, says Perk chose Make for its easier learning curve, its built-in integrations, and its price. Builders need some knowledge of APIs and JSON, so Stock coordinated their training, and Perk is opening Automation Engineer roles embedded in each department. The account comes from Make's own customer story, published March 12, 2026.
Methodology
GILD read 55 public accounts published January 1, 2025 through September 28, 2026. They comprise 22 Make Community posts, 16 Reddit posts and comments, 5 Hacker News comments and story texts, and 5 personal and company blog posts. The rest are 1 GitHub issue, 1 X post, 1 n8n Community post, and 4 named accounts from Make customer stories. Because r/Integromat is a help forum, GILD capped Reddit at about a third and chose the highest-scored first-hand accounts. GILD opened and tagged the original records on October 12, 2026 and checked product facts against Make's pages that day. It reread the four customer pages on October 26. Counts tally these accounts and do not stand in for a customer survey. Forum posts make up 23 of the 55 and lean toward problems. Of the four named customer accounts, one is a transformation leader and one an engineering team. The other two are business units running Make in production.
Products in this piece
Sources
- Official documentation
- 6
- Public source
- 15
- Make pricing
- Make Help Center: Credits
- Make Help Center: Operations
- Make Help Center: Introduction to Make AI Agent (New)
- Make Help Center: Make MCP server
- René Zander: Migrate Zapier to Make, a practitioner's guide (Apr 8, 2026)
- Rahul David Mondal: Why I switched to Make.com before paying a cent (Jun 27, 2026)
- Make Community: How we reduced 720K+ operations annually using custom variables (Nov 19, 2025)
- Make Community: Victor Blanco on the move to credits (Aug 28, 2025)
- Make Community: Asana usage running when there's no new activity (Mar 4, 2026)
- Make Community: Extra credits reset? (Aug 28, 2025)
- Reddit r/Integromat: Anyone else getting killed by Make operation costs? (Feb 26, 2026)
- Make Community: Service Outage, November 12th (Nov 13, 2025)
- Make Community: Instagram module failing with Media ID is not available (Nov 12, 2025)
- Make Community: Automation workflows, managing many client scenarios (Sep 28, 2026)
- Reddit r/Integromat comment on Make scenarios for overdue QuickBooks invoices (Jan 1, 2025)
- Make Community: New AI-Agents feedback (Mar 19, 2026)
- Make Community: Agents MCP server with OAuth2? (Oct 26, 2025)
- Hacker News: replacing about 15 Make scenarios that broke silently (Mar 10, 2026)
- Hacker News comment on moving from Make to n8n for loops and code (May 3, 2025)
- Make customer story: How Perk unlocked efficiencies with Make automation (Gabriel Stock, Mar 12, 2026)