Relay.app has closed. Here is where the work goes.
Relay.app shut down in September 2026, and its site now says every account has been deleted. Start from what you exported, or from what you remember, and sort it into two piles. Read on relay.app on 11 and 26 September 2026.
- Relay.app has closed. Its site now says all accounts, workflows and run history have been permanently deleted.
- If you exported in time, you hold your Workflows, Sequences and MCP servers as JSON and AI prompts, plus CSVs of run history and tables.
- Annual customers were promised an automatic prorated refund for the unused part of the billing period.
- Do not rebuild everything. Most accounts held a few automations that earned their keep and a long tail nobody will miss.
- Sort what is left into two piles. Fixed steps belong in a workflow tool, and judgment calls belong with a colleague.
What happened, in their words
Relay.app gave notice early and kept to it. Free accounts stopped on 15 August 2026 and paying customers on 14 September, with signups and upgrades turned off before that. Customers could export "Workflows, Sequences and MCP servers as JSON and AI prompts so you can rebuild them elsewhere", plus run history and tables as CSVs. Annual customers were told "we will automatically initiate a prorated refund for the unused remainder of the current billing period."
The site now shows a single notice: "Relay.app shut down in September 2026. All accounts, workflows, and run history have been permanently deleted." Stored credentials and tokens for connected apps went with the rest, as the notice said they would.
Their notice recommended nowhere to go, which is a fair choice for a company closing. What follows is our honest read, and it sends much of the work to other products.
What to do now
About an hour of work, most of it in the first two steps.
- 01
Find what you exported
Look for the JSON of your Workflows, Sequences and MCP servers, and the run history CSV. If nobody exported, list the automations from memory and from the apps they touched.
Relay's site says nothing is left to download.
- 02
Revoke Relay's access in your apps
Relay says it deleted the stored credentials and tokens. Revoking its access on your side closes the loop, and it shows you which tools were wired up.
- 03
List what actually ran
Use the run history CSV if you have it. In most accounts a handful of automations did nearly all the runs, and the rest were built once and forgotten.
Rebuilding the forgotten ones is the most common way a migration turns into a month.
- 04
Sort the survivors into two piles
Pile one does the same steps in the same order, on a trigger. Pile two needed a person to read the situation and decide, which is often where Relay's human-in-the-loop steps sat.
- 05
Rebuild pile one, hand over pile two
Pile one belongs in a workflow tool, where a diagram you can inspect is exactly right. Pile two needs no rebuild, because the judgment was the work.
Where each kind of work should land
Two of these rows point away from us, because another tool fits that work better.
| What you had in Relay | Rebuild it in | Or hand it to Cedric |
|---|---|---|
| A trigger that always does the same steps | Zapier or Make, whichever app list covers your tools | A workflow tool fits fixed steps better |
| Technical, self-hosted, kept in version control | n8n, with the source on your own servers | n8n fits: you own the code and hosting |
| A step that paused for a human to approve | Rebuildable, and the fiddly part of any canvas | Built in: a person says yes each time |
| An automation that kept needing new branches | The branches will come back | Ask for the outcome; decided per request |
| Reading a message and deciding what it deserves | Hard to express as a flowchart | The job he was built for |
| A recurring report pulled from several tools | Possible, and brittle when a source changes | Ask once; posted on your schedule |
Relay's human-in-the-loop steps are the tell. If many of your automations paused for a person, the work never had fixed steps, and a flowchart with approval gates rebuilds the wrong thing. To compare n8n with the tools people pick instead, see the n8n alternatives.
Pile two
Work that needs reading, not routing
Lena Brunner9:14 AM
@Cedric catch me up, I was out all week.
CedricAPP9:15 AM
Your week, 3 to 9 September: two client contracts wait for your signature, and Maya needs your ok on the September ad budget. Meridian, Volta and Studio Nord signed, and signups doubled after the new website went live. One gap: I did not open the notes of the two weeklies you missed. I can pull those, or tell Maya you approve the budget.
No rebuild
Nothing to draw. Connect the tools once, then ask in Slack, Microsoft Teams, Discord, Telegram or the browser.
He names his gaps
He said which notes he had not read instead of guessing. Sorting a week by what waits on you is a judgment, not a route.
The pause comes built in
The message to Maya waits on Lena's yes. Nobody had to remember to add that step.
A fair word about Relay
Relay was a thoughtful product, and early to the idea that a person belongs inside an automation rather than bolted onto the end. That idea was right, and it now shows up everywhere, including here. A company closing says something about a market and a runway, and very little about whether the software was good.
The wind-down was handled well too. The dates came with enough warning to act on, the export was real, and refunds on annual plans were automatic.
If your work has fixed steps, go to Zapier, Make or n8n; each is a good home for it. This page was first written on 11 September 2026, three days before the paid cutoff, and updated after the shutdown on 26 September.
FAQ
No. The export closed with the service, and the site now says everything was deleted. Rebuild from memory and from the apps each automation touched.
Cedric works from a sentence rather than an imported workflow. Describe the outcome, and he works out the steps each time. If you exported, keep the JSON as a record of what each automation did.
That is the clearest sign the work needed judgment rather than a route. In Cedric, anything that sends, changes or spends holds for a yes by default, so those automations tend to become a sentence.
Probably not. Most teams end up with a workflow tool for the fixed plumbing and a teammate for the work that needs reading a situation.
Starter is $19 a month for 40,000 credits, for the whole team. Sign-up gives 100,000 credits with no card, enough to move a few automations and see how they run.
Move the judgment work, not the flowcharts.
100,000 free credits, no card. Start with the automation you miss most.
100K credits ($50) through Slack, Teams, Discord, Telegram or WhatsApp, 50K ($25) with Google. No card needed.