Make
Automation · Freemium
Overview
A visual automation platform. You build workflows, called scenarios, by placing modules on a canvas and drawing lines between them, where each module does one job such as reading a new spreadsheet row or sending a message. The product was first known as Integromat, built by a Czech team, and was renamed Make in 2022. It is owned by Celonis. Make aims to sit between simple trigger-and-action tools and full custom code, so people can build automations with branching, loops, and data reshaping without a developer. Scenarios can run on a schedule or fire instantly from a webhook.
What people use it for
Teams use Make to move data between systems that do not talk to each other, such as copying a new CRM contact into a billing tool and a spreadsheet at the same time. Marketing teams use it for lead routing, record enrichment, and posting content across channels on a schedule. Operations teams build order processing flows that check stock, create invoices, and notify staff, with different paths for different order types. Support teams use it to triage tickets, tag them, and escalate based on rules. Others call an AI service in the middle of a flow, for example to summarize a document or classify a message before the next step runs. Because a scenario can branch and loop, people reach for Make when a job has several conditions or needs to process a list of items one by one.
Key capabilities
Make lists more than 3,000 pre-built app connectors, plus over 300 apps for generative AI services. When no connector exists, the HTTP and webhook modules let a scenario call any public API or receive data from outside. The canvas supports routers for branching, filters on any path, iterators to loop through lists, and aggregators to combine results back together. Error handling is built in, so you can attach a handler to a module to retry, ignore, or take a recovery path when a step fails. Make Code lets you write JavaScript or Python inside a scenario, and built-in functions reshape data without code. Make also offers AI Agents that can call scenarios as tools, an MCP server, and Maia, an assistant that builds automations from a description. For larger customers there is role-based access control, SSO, a SOC 2 Type II report, and Make Grid, a generated map of every automation in an account.
Limitations
The learning curve is steeper than trigger-and-action tools. Routers, iterators, and data structures take time to understand, and small mapping mistakes are hard to spot. Large scenarios get crowded on the canvas and slow to read, and tracing why a flow broke can mean stepping through many modules. Pricing runs on a usage count, so a flow that touches many records uses up the monthly allowance quickly, and heavy users move up tiers or buy extra bundles. Some connectors lag behind the underlying app's API and miss newer endpoints. Moving a complex scenario to another platform means rebuilding it, since the logic is specific to Make.
Insight
Make earns its place when an automation has real logic in it: several branches, a list to process, a lookup in the middle. Zapier can be forced to do this but it gets awkward, while Make was built for it and the canvas keeps the shape visible. The cost is upfront. Someone has to learn how routers, iterators, and data structures behave, and that person often becomes the only one who can safely change the flow. On big scenarios the canvas turns into a wall of modules, and finding the one bad step after a failed run is slow work. The usage-based pricing also rewards tight design and punishes sloppy loops. It is the right tool when the job is past what Zapier handles cleanly but not worth a developer's time to code.
Pricing
Freemium
Website
Last checked 2026-08-30