What happened, and what it means for you
Integromat is Make now.
Here is what that means.
If you are searching for Integromat, one of three things is true: you used it years ago, you inherited scenarios somebody else built, or you are trying to work out whether it still exists. It exists, under a different name. Celonis acquired Integromat in October 2020, and in February 2022 the product was rebranded to Make. Your scenarios did not disappear. What did change is the pricing model, the surrounding platform, and the question of how far this tier can carry you.
Want to know what this costs in your shop?
I will work out your three biggest time sinks, in hours and dollars. Free, in writing, within 72 hours.
No newsletter, no sequence. You keep the analysis either way.
Tim Muenzel
builds and runs the systems himself
What actually changed
The engine most people liked is still there: a visual canvas, real branching, iterators and aggregators, error handlers, and a price per operation that undercuts the better-known alternatives. What changed around it is the packaging. Make positions itself as a broader platform rather than a connector tool, the plan tiers were restructured, and the operations counter became the number that decides your bill. For a scenario that runs a handful of times a day, none of that matters. For one that touches every order, it matters a lot, because the cost now scales with your success rather than with your usage of the tool.
Where it is still exactly the right answer
A form response that has to reach a spreadsheet and a chat channel. An order that triggers a notification and a record. A nightly sync between two systems whose shape rarely changes. In that territory Make is genuinely hard to beat, and anyone who tells you to build custom software for it is selling you something you do not need. The tier exists because most integration problems really are that simple, and solving them in twenty minutes instead of two weeks is a real advantage.
The inherited-scenario problem
The most common reason people search for Integromat today is not curiosity. It is that a business depends on scenarios somebody built years ago, that person is gone, and nobody dares to touch them. This is the specific failure mode of the whole tier: the canvas is readable while you are building it and unreadable a year later, because the logic lives in the layout rather than in anything you can review, test or hand over. If that is your situation, the first task is not migration. It is writing down what the scenarios actually do, because that document is the thing you are missing, not a different tool.
The four signals that you have outgrown the tier
One: the operations bill grows faster than the value the automation creates. Two: exactly one person understands what runs where, and nobody wants to change it. Three: the workarounds have quietly become the system, whether that is a data store standing in for a database or code modules holding the real logic. Four: something failed and you found out from a customer rather than from the system. The fourth one is no longer a tool question, it is operational risk, and switching between Make, Zapier and n8n does not touch it, because none of the three can tell you that a run did not happen.
If you need someone to look at an existing setup
I do not build in Make and I do not sell migrations as a product. What I do is a free written analysis: you tell me what the scenarios are supposed to do and where they hurt, and within 72 hours you get back what the manual work around them costs per year, which parts genuinely belong in a tool, and which one process would be worth owning outright. If the honest answer is that your setup is fine and needs documenting rather than replacing, the analysis says that, and it costs you nothing either way.
When owning beats renting, in numbers
A scenario that processes every order, running roughly 40,000 operations a month on a mid-tier plan, plus the person who watches it:
| Plan and operations | roughly $100 to $200 per month at that volume |
|---|---|
| Three-year subscription cost | roughly $3,600 to $7,200, and it keeps running |
| The part nobody counts | the hours spent checking whether last night actually ran |
| Owned equivalent, built once | from $6,900 fixed scope, then nothing to rent |
| What you also get | tests, monitoring that reports failures, and code you can hand to anyone |
| Where renting still wins | anything under roughly 5,000 operations a month, clearly |
This is deliberately not stacked in favour of building. Below a few thousand operations a month the subscription wins outright and the teardown will say so. The line moves the moment a failed run costs money rather than patience.
Common questions, answered straight
Is Integromat dead?
No. It was renamed. Celonis acquired it in October 2020, and the product was rebranded to Make in February 2022. Existing accounts and scenarios carried over rather than being shut down.
Do my old Integromat scenarios still work?
In general yes, they run under Make. What changed is the plan structure and how operations are counted, so the bill may look different from what you remember even if the scenario is unchanged.
Do you build or fix scenarios in Make?
No. I build custom code and operate it in production, and I moved my whole practice that way after years of building in the workflow tier, including a self-hosted n8n production pipeline. That is exactly why my recommendation is worth something: if your problem belongs in Make, I have nothing to sell you, and I will say so.
We inherited scenarios nobody understands. Where do we start?
With documentation, not migration. Write down what each scenario is supposed to achieve and what breaks if it stops. That document is what makes every later decision cheap, including the decision to keep everything exactly as it is.
What would replacing one process cost?
Published rather than negotiated: the analysis is free, a systems audit is $490 and is credited toward the build, and a fixed-scope build sprint starts at $6,900 with the final invoice only when it runs in production.
Related reading
Inherited a setup nobody understands?
Free systems teardown: what the manual work around your scenarios costs per year, which parts belong in a tool, and which single process would be worth owning. In writing, within 72 hours, no obligation.
Get your free systems teardown