The visual automation platform for teams whose processes have branches.
Make is the automation layer teams graduate to when linear, per-task tools stop being enough. Everything happens on a scenario canvas: routers split logic, iterators walk arrays, aggregators recombine them, error handlers keep processes alive, and AI modules add classification or drafting mid-flow. This hub tracks every part of the Make platform, how the pieces fit, and how to build scenarios that stay cheap at volume.
The core visual builder — triggers, routers, filters, iterators, aggregators, data stores and error handling on a single readable canvas.
Model providers as ordinary modules plus Make AI Agents for tool-calling flows where the branching is genuinely open-ended.
Thousands of native apps, a generic HTTP module for any documented REST API, and a custom-app framework for reuse.
Visual workflow automation with real branching logic.
Scenarios are the heart of Make. Each module is a typed operation with explicit input and output mapping, which is what makes multi-branch business logic practical to build and — more importantly — practical to maintain six months later.
AI steps inside deterministic workflows — plus tool-calling agents.
Make's AI surface has two halves: model providers as ordinary modules for classification, extraction and drafting, and AI Agents that decide which tools to call. Because both live on the same canvas, you can wrap an agent in deterministic guardrails instead of choosing between the two.
Thousands of native connectors, plus anything with an API.
The app catalogue spans CRM, ecommerce, finance, marketing, support and data tooling. For serious builds the more important capability is the generic HTTP module and the custom-app framework, which turn 'not supported' into 'not yet packaged'.
Shared workspaces, roles and governance for automation at scale.
Teams and Enterprise plans exist for the moment automation stops being one person's side project: shared workspaces, role-based access, higher operation ceilings and organisation-level controls. Enterprise terms are quoted, so treat published capability lists as the starting point for a procurement conversation.
Run both in parallel, cut over one process at a time, and verify with logs.
Operations discipline matters more than the plan you pick.
Yes — Integromat was rebranded to Make, and the platform kept its dataflow engineering heritage.
Per operation, roughly one per module execution, across free, Core, Pro, Teams and Enterprise tiers.
Yes on day one, and that is the trade: routers, iterators and mapping are what make complex processes maintainable later.
The first month of the Pro plan — 10,000 operations — is free through our partner link, after which standard pricing applies.
