Make: What Users Actually Complain About

Make (formerly Integromat) markets itself as a visual automation platform that’s more powerful than Zapier but easier than code. The pitch works — until you’re three hours into debugging a scenario that should have taken fifteen minutes, realizing their pricing calculator didn’t warn you about operation bloat, and discovering that the “intuitive” interface has a learning curve steeper than you expected.

The platform does deliver on power. You can build complex workflows with routers, filters, and data transformation that would require multiple Zapier zaps. But that power comes with friction that small business owners consistently report: unpredictable costs, time-intensive setup, and support that doesn’t match the complexity of the tool.

The Operation Count Problem Nobody Warns You About

Make’s pricing is based on operations, not tasks. That distinction matters more than their marketing suggests. A single automation might consume ten operations when you expected two. Every API call counts. Every data transformation counts. Every filter, even if it stops the workflow, counts.

Users regularly report scenarios where a workflow they assumed would cost 1,000 operations per month actually burned through 5,000. The free tier offers 1,000 operations monthly — which sounds generous until you realize a moderate email-to-spreadsheet automation can hit that in a week. The $9/month Core plan gives you 10,000 operations, but for businesses running multiple scenarios, that ceiling arrives faster than expected.

Zapier’s task-based pricing is simpler to predict. You know what you’re paying. With Make, you’re estimating, then monitoring, then adjusting when your bill doesn’t match your assumptions.

The Interface Is Powerful — And Exhausting

Make’s visual builder looks impressive in demos. Drag modules, connect lines, build flows that branch and merge. But what feels empowering in a tutorial becomes tedious in daily use. Setting up error handling requires extra modules. Parsing JSON means clicking through nested menus. Simple “if this, then that” logic requires routers, filters, and careful connection management.

The most common complaint from former users: it takes too long to build and maintain scenarios. A workflow that would take ten minutes in Zapier might take an hour in Make — not because Make can’t do it, but because the interface demands more clicks, more configuration, more troubleshooting when something breaks.

For technical users comfortable with APIs and data structures, this is acceptable overhead for advanced features. For small business owners who just need Gmail to talk to their CRM, it’s friction without benefit.

Support Doesn’t Match the Complexity

When you’re stuck debugging a scenario at 10 PM before a launch, Make’s support options feel thin. The free and Core tiers get community forum support — no direct help. The Pro tier ($29/month, 40,000 operations) adds email support, but response times vary. Users report waiting days for answers to specific technical questions.

Compare this to alternatives built for less technical users. Zapier offers email support on paid plans starting at $29.99/month. ActivePieces, an open-source Make alternative, has responsive community support and transparent documentation. For tools this complex, support quality matters.

Who Should Use Make vs. Alternatives

Make works if you’re building multi-step workflows that genuinely need routers, iterators, and advanced data manipulation — and you have time to learn the platform. It’s overkill if you’re connecting two apps with straightforward logic. [CTA: Try Zapier] for simple automations with predictable pricing, or explore [CTA: Try ActivePieces] if you want Make-like power without the operation count anxiety.

The verdict: Make isn’t overpriced for what it does, but it’s over-complicated for what most small businesses need. Unless your workflows require branching logic and complex transformations, simpler tools will save you time and mental overhead.

StackSmall – June 2026