The tool is gone. The problem is not.
Automate.io is gone.
Here is what replaces it.
If you are looking for Automate.io, the search results are probably confusing you, because half of them still describe a product that no longer accepts customers. Notion acquired Automate.io in September 2021 and the product was shut down on 31 October 2022, with a six-month off-boarding window and a Zapier offer for paying customers. The tool is gone. The processes it was running are not, which is the only reason this page is worth reading.
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
Where its users actually landed
Most went to Zapier, because that was the migration path on the table and the switch cost nothing for a year. A smaller group moved to Make, which was cheaper per operation and handled branching better. A few went to self-hosted n8n, usually the ones with somebody technical in the building. And a fourth group did nothing, which means the automations quietly stopped and the work went back to a person. That fourth group is larger than anyone admits, and it is the reason processes get re-discovered years later as "we used to have something for that".
What the shutdown should have taught everyone
Automate.io did nothing wrong. It was a decent product with real customers, and it disappeared because its owner was bought and the acquirer wanted the team, not the product. That is a normal outcome in this category, and it will happen again. The lesson is not to avoid tools. The lesson is to know which of your processes would survive the tool disappearing, and which would simply stop. If a process would stop and that would cost you money, it belongs somewhere you control.
The honest replacement, in order
For a linear connection between two apps that runs a few times a day, use Zapier and stop reading. For scenarios with branching and moderate volume, use Make, which is the same tier at a better rate per operation. If you have someone who can run a server and ownership matters, self-hosted n8n removes the per-task fee entirely. And if the process is one your business genuinely depends on, none of the three is the answer, because none of them can be tested, reviewed or handed over the way software can.
The migration nobody plans for
The hard part of leaving a shut-down tool is never rebuilding the flows. It is that nobody wrote down what they did. Automations accumulate silently for years, and the documentation is the layout of a canvas that no longer exists. Before you pick a replacement, write down for each automation what it was supposed to achieve, what triggered it, and what breaks if it does not run. That document is worth more than the choice of tool, and it is the thing you will be missing again the next time a vendor is acquired.
What the replacement decision actually costs
A mid-sized set of automations, roughly what a company on Automate.io would have had, priced over three years:
| Zapier, mid plan | roughly $70 to $100 per month, scaling with tasks |
|---|---|
| Make, comparable volume | usually less per operation, same shape of bill |
| n8n, self-hosted | a server bill instead of a per-task fee, plus somebody to run it |
| Owned code, built once | from $6,900 fixed scope, then nothing to rent |
| The cost nobody prices | the week spent working out what the old automations did |
| Where a subscription clearly wins | anything small, linear and not business-critical |
This table is not stacked toward building. For the majority of what ran on Automate.io, a subscription is still the right answer and always will be. It stops being the right answer at the point where a failed run costs money rather than patience.
Common questions, answered straight
When exactly did Automate.io shut down?
Notion announced the acquisition in September 2021, and the product was shut down on 31 October 2022 after a six-month off-boarding period. Paying customers were offered twelve months free on Zapier as a migration path.
Can I still export my old Automate.io setup?
No. The service is off, so whatever was not exported before the deadline exists only in whatever notes people made. That is exactly why the first step now is reconstructing what the automations were supposed to do, not choosing a tool.
Is Zapier the safe choice because it is bigger?
Bigger, yes. Safe is a different question. Every tool in this tier holds your logic in a place you cannot review, test or take with you. Size reduces the odds of a shutdown; it does not change what happens to your process if one occurs.
Do you sell migrations?
No. I build custom systems and run them in production, and I do not build in Zapier, Make or n8n. If your case belongs in one of those, my analysis says so by name and a specialist will do it far cheaper than I could.
What would owning one of these processes cost?
The analysis is free and written. A systems audit is $490 and is credited toward the build. A fixed-scope build sprint starts at $6,900, with the final invoice only when it runs in production.
Related reading
Automations that stopped when the tool did?
Free systems teardown: what the manual work costs you per year now that they are gone, which ones belong in a subscription, and which single process would be worth owning. In writing, within 72 hours.
Get your free systems teardown