Make: What It Actually Does, What It Costs, and Who It Fits
A visual, canvas-based automation builder for complex, branching, multi-step workflows, aimed at teams that want to see and control the full data flow, not just chain a trigger to an action.
Make is the right pick for a team whose automations have outgrown a simple trigger-action chain, multiple branches, error handling per step, and real data transformation that a linear builder struggles to represent clearly. It generally asks more of a new user up front than a tool like Zapier does, but for teams building multi-step scenarios regularly, its visual canvas and operations-based pricing tend to go further for the money on complex work.
What Make Is For
Make (formerly known as Integromat, rebranded in 2022) is a workflow automation platform built around a visual, canvas-based scenario builder rather than a linear step list. Every module in a scenario sits on the canvas as a node, connected by lines that show exactly how data flows and branches between them, including routers that split a single trigger into multiple parallel paths, filters that add conditions, and iterators or aggregators that handle arrays of data. That structure makes genuinely complex automations much easier to see, build, and debug than a simple trigger-then-action chain.
It's built for technical marketers, operations teams, and agencies who regularly build multi-step, branching automations and want direct control over data mapping and error handling at each step, not just at the workflow level. Teams that only need to connect two apps in a simple, linear way sometimes find Make's canvas more setup than the job requires, which is where a simpler tool like Zapier tends to be the faster starting point.
Key Features
- Visual, canvas-based scenario builder showing the full path data takes across every module
- Routers and filters for branching a single trigger into multiple parallel, conditional paths
- Iterators and aggregators for working with arrays and bundling data back together
- Built-in error handling and retry logic configurable at the individual module level
- Operations-based pricing that can be more cost-effective than task-based billing for complex, multi-step scenarios
- Growing app library plus generic HTTP and webhook modules for connecting to almost any API
Pros & Cons
Pros
- ✔ Visual canvas makes complex, branching logic easy to see and debug, a genuine advantage over linear, list-style builders
- ✔ Operations-based pricing can be more cost-effective than Zapier's task-based model for complex, multi-step scenarios
- ✔ Deep control over data mapping, error handling, and retries at the individual module level
Cons
- ✕ Steeper learning curve than a tool like Zapier, the visual canvas rewards technical comfort more than a simple linear list does
- ✕ Smaller native app catalog than Zapier, though generic HTTP modules cover much of the gap for less common tools
- ✕ Operations consumption can be hard to predict in advance for a genuinely complex, high-volume scenario
Pricing
Make has a genuinely usable free tier.
| Tier | Price (billed annually, entry operations tier) | What you get |
|---|---|---|
| Free | $0 | 1,000 operations/month, 2 active scenarios, core app library |
| Core | Roughly $9 to $12/month | 10,000 operations/month, unlimited active scenarios, full execution history |
| Pro | Roughly $16 to $21/month | Higher operations ceiling, priority scenario execution, custom variables |
| Teams | Roughly $29 to $38/month | Team collaboration, shared scenario folders, higher operations ceiling |
| Enterprise | Custom pricing | Dedicated infrastructure, SSO, custom operations volume, dedicated support |
Every paid tier's price scales up with the number of operations purchased, the figures above reflect the lowest available operations tier on each plan, a heavier scenario volume moves the same plan into a pricier bracket.
Pricing checked as of late 2026 and hedged as approximate - Make adjusts operations allotments, tier pricing, and plan names periodically, so confirm current figures directly on Make's pricing page before budgeting.
Common questions
Generally, yes, though not dramatically so. Make's visual canvas asks a new user to think in terms of data flow and branching modules rather than a simple linear list, which takes a bit more time to get comfortable with but pays off once a workflow gets genuinely complex.
Integromat was rebranded to Make in 2022. It's the same underlying platform, expanded and renamed, it still uses an operations-based consumption model similar to the original product.
It depends on the shape of the workflow. For a complex, multi-step scenario, Make's operations-based pricing is often more cost-effective than Zapier's task-based billing, since a single Zapier task can map to several linked steps inside one Make scenario. See our full Zapier vs Make comparison for the detailed breakdown.
Not sure if Make is the right fit for your automation stack?
We'll look at how complex your workflows actually are, and how much branching and data transformation they need, before recommending a platform.
Ready to get started?
We usually reply within 24 hours.