Make (formerly Integromat) Review

Make is a visual automation platform that allows you to connect apps, automate workflows, and move data between systems without writing extensive code. It evolved from the earlier product Integromat and now positions itself as a flexible tool for individuals, teams, and enterprises. The core idea is to let you design workflows, called scenarios, using a drag‑and‑drop interface that chains together triggers, actions, and data transformations.

Where many automation tools focus on simple one‑to‑one connections, Make is built for multi‑step, branching workflows that can handle complex business logic. You can combine multiple apps, conditional paths, and data processing modules in a single scenario. This makes it suitable not just for basic automation, but also for building lightweight internal tools and integration layers between your existing systems.

Make is commonly used for marketing automation, CRM synchronization, operations workflows, and connecting SaaS tools that do not natively talk to each other. It also appeals to technical users who want a more visual way to orchestrate APIs and background jobs. At the same time, non‑technical users can start from templates and gradually learn the more advanced capabilities as their needs grow.

The core value proposition of Make is its visual scenario builder, which lets you design sophisticated automations by connecting modules on a canvas. Each module represents an app, API call, or data operation, and you can chain them together with filters, routers, and error handlers. This approach makes complex workflows more understandable and maintainable than traditional script‑based solutions.

Another key strength is the platform’s depth of integrations and data handling. Make supports thousands of apps and offers generic HTTP, webhook, and database modules for anything not covered by native connectors. You can map fields visually, transform data on the fly, and reuse logic across multiple scenarios, which is particularly valuable for teams managing many similar workflows.

Make also positions itself as a bridge between no‑code and pro‑code. Business users can build automations from templates, while developers can extend scenarios with custom API calls, JSON transformations, and advanced error handling. This dual appeal makes it a strong candidate for organizations that want to empower non‑technical staff without locking out technical teams.

Make’s flagship feature is its drag‑and‑drop scenario builder, where you visually connect triggers and actions across multiple apps. You can add routers to create branching paths, filters to control data flow, and aggregators to combine or split data sets. This makes it possible to model complex business processes that go far beyond simple “if this then that” automations.

The platform offers a large catalog of prebuilt app integrations, covering popular tools in CRM, marketing, project management, collaboration, and e‑commerce. When a native integration does not exist, you can fall back on webhooks and HTTP modules to call any REST API, making the platform effectively universal. Data mapping is handled through a visual interface where you can reference fields from previous steps and apply functions to transform values.

Make includes robust scheduling and execution controls, allowing scenarios to run on intervals, in real time via webhooks, or on demand. You can set limits on operations, configure error handling and retries, and monitor execution history with detailed logs. For teams, there are collaboration features such as shared workspaces, role‑based access, and versioning options that help keep complex automation projects under control.

Developers benefit from advanced modules and extensibility. You can work with JSON, arrays, and complex data structures, and you can chain multiple API calls with conditional logic. Combined with the visual interface, this makes Make a compelling alternative to writing custom integration scripts from scratch, especially when requirements change frequently.

Because direct access to Make’s pricing page is currently blocked by a protection layer, the following overview is based on widely reported public information and may not reflect the latest exact numbers. Historically, Make has offered a Free plan with limited operations and scenarios, alongside several paid tiers that scale in operations, data transfer, and collaboration features. The paid plans are typically structured around monthly operation quotas and additional capabilities for teams and enterprises.

Commonly referenced tiers include an entry‑level Core or Starter plan, a mid‑range Pro plan, and higher Teams and Enterprise plans. As you move up the tiers, you generally gain more operations per month, higher data transfer limits, priority support, and advanced governance features. Enterprise customers usually receive custom pricing based on usage, security requirements, and onboarding needs.

Given that Make’s pricing is usage‑based, it is important to estimate how many operations your scenarios will consume. Complex, high‑volume workflows can quickly move you into higher tiers, while smaller teams with targeted automations may find the lower plans sufficient. Always verify the latest pricing directly on Make’s site, as quotas, names, and features can change over time.

Public feedback about Make often highlights its power and flexibility as major advantages. Users frequently report that complex workflows which would require custom code can be built visually in Make, saving development time and maintenance effort. At the same time, some reviewers note that the learning curve can be steep for non‑technical users who are new to automation concepts.

Customers also praise the breadth of integrations and the reliability of scheduled and webhook‑based executions. It has been mentioned that the platform’s scenario logs and error handling tools make debugging easier compared with simpler automation tools. However, a recurring concern is that heavy usage can become expensive, and that complex scenarios require careful monitoring to avoid hitting operation limits.

Below are paraphrased examples of typical customer sentiments gathered from public reviews and discussions, rewritten in passive voice for clarity and SEO purposes. These quotes are representative rather than official testimonials from Make’s own site, due to limited direct access at this time.

From a capabilities standpoint, Make stands out as one of the most feature‑rich automation platforms available today. Its visual scenario builder, extensive integrations, and advanced data handling make it suitable for serious automation work, not just simple task chaining. For organizations that want to centralize integrations without building a full internal platform, Make can serve as a powerful backbone.

The trade‑off is that this power introduces complexity and cognitive load. New users may find the interface overwhelming, especially when scenarios involve many branches and data transformations. Documentation and templates help, but teams should plan for onboarding time and internal best practices to keep automations maintainable.

In terms of value, Make can be very cost‑effective for medium‑complexity, medium‑volume use cases. As usage scales, however, operation‑based pricing and scenario complexity can increase both cost and management overhead. Teams that only need narrow, content‑focused automation—such as social posting—might find more specialized tools easier to adopt and maintain over time.

Make is a strong choice if you need flexible, visual automation that can handle complex, multi‑step workflows across many different apps. It shines in environments where both business users and developers collaborate on integrations, and where requirements change often enough that custom code would be costly to maintain. For teams willing to invest in learning the platform, the payoff in automation coverage and agility can be substantial.

On the other hand, Make may be overkill if your needs are limited to a few simple automations or a single channel, such as social media posting. The learning curve, operation‑based pricing, and scenario complexity can feel heavy compared with leaner, purpose‑built tools. In those cases, a specialized solution that focuses on one domain can deliver faster time to value with less ongoing management.

Overall, Make earns a strong rating for its depth, flexibility, and ability to replace custom integration code in many scenarios. It is best suited for teams that treat automation as a strategic capability rather than a side project, and that are comfortable managing a powerful but complex tool. If that describes your organization, Make is very likely to be worth serious consideration.