Relay.app Is Shutting Down: The Practical Migration Guide

On July 16, 2026, Relay.app announced it is winding down. Free accounts, and all their data, are permanently deleted after August 15, 2026 at 23:59 PT. Paying customers keep free access until September 14, 2026 at 23:59 PT, and then their accounts and data are deleted too. New signups are already closed.

If you run workflows on Relay, you now have two jobs: secure your data, and decide where your workflows run next. This guide covers both, in that order, because the first one has a hard deadline and the second one does not have to be rushed.

The dates that matter

August 15, 2026, 23:59 PT — free accounts and all associated data are permanently deleted.
September 14, 2026, 23:59 PT — paid accounts and all associated data are permanently deleted. Until then, paying customers keep full access for free, with extra monthly steps and AI credits Relay added to ease the transition.
Annual customers receive an automatic prorated refund for the unused part of their billing period.
When an account is deleted, Relay's stored credentials and tokens for connected apps are deleted with it.

There is no recovery after these dates. Everything else in this guide can be done calmly; the export cannot.

Step 1: Export everything now, even before choosing a new tool

In your Relay dashboard, choose Export workspace data. The export is prepared as a .zip file, which can take up to 24 hours for large workspaces, and the download link you receive by email is valid for 48 hours.

The zip contains a folder for every workflow, sequence, MCP server, and table in your workspace, including:

a build prompt (a .md file) that describes the workflow so it can be rebuilt in another tool
a JSON file with the exact structure of the workflow
run history as CSV, plus a JSON file per run
table data as CSV, where applicable

Workflow screenshots are the one thing not included — if you want a visual record, use Save workflow as screenshot inside each workflow before the deadline.

Do this today, even if you have not decided where you are going. Every other step in a migration can wait a week. This one cannot.

What to look for in a replacement

Relay users did not pick Relay for its trigger catalog. Most picked it because it treated AI as a worker and humans as supervisors: AI steps did real work, and human-in-the-loop steps let you approve the parts that mattered before they happened.

If that is why you chose Relay, a classic trigger-action tool will feel like a downgrade. Whatever you evaluate, check four things:

Human-in-the-loop is a first-class concept, not a workaround. You should be able to put an approval in front of any consequential step.
AI steps are native. Drafting, extracting, deciding, and summarizing should be normal steps, not an add-on module.
You can build from a description. Your Relay export gives you each workflow as a prompt — the fastest rebuild path is a tool that accepts one.
Your tables have somewhere to live. Relay Tables export as CSV; the replacement should import them as structured data, not attachments.

Relay's own migration advice, and why it matters

Relay's export documentation is honest about a detail most migration guides skip: every workflow builder structures workflows differently, so Relay's JSON export will not load into other tools' native importers. Their recommendation is to use the generated build prompts instead, because "prompts are the best way to rebuild workflows" in another tool.

That advice describes AgentLed's normal mode of operation. AgentLed's builder is prompt-native: you describe a workflow in natural language, the AI builds it, and you review the draft before anything runs. Relay's recommended migration path is not a workaround here — it is simply how the product works.

The migration path, step by step

Export your workspace (see above).
Pick the workflows that matter. Your run history CSVs make this honest: sort by recent runs and migrate what actually executes, not what accumulated over the years.
Rebuild from the build prompt. Open a new workflow in AgentLed and paste the .md build prompt from your export. The builder produces a draft: steps, order, and logic, ready for review. Nothing runs until you approve it.
Put approvals where you want them. Recreate your human-in-the-loop steps as approval gates — same concept, same purpose.
Reconnect your apps. Relay deletes all stored app credentials at shutdown, so every tool you move to requires reconnecting your apps. Budget the time once, wherever you land.
Import your tables. Relay Table CSVs import into AgentLed as Knowledge Lists.
Run in parallel. Relay keeps working until your deadline. Run both side by side and compare outputs before you switch anything off.

We are also building a native Relay importer that reads the workflow JSON for structure alongside the build prompt for intent, so whole-workspace migrations get easier. If you want to hear when it ships, email us.

If you would rather not do this yourself

During the wind-down we are offering Relay users a direct path: send us your export — or just the build prompts of the two or three workflows you care about — and we will rebuild your top 3 workflows on AgentLed, free. You get free access through September 14, so you can judge the result running before you pay anything.

Write to ouadie@agentled.ai with your export attached. A founder reads and answers every one of these.

The short checklist

Export your workspace data today; the download link lasts 48 hours once ready.
Save screenshots of any workflow you want a visual record of.
Use run history to decide what is worth migrating.
Rebuild from build prompts — yourself, or send them to us.
Reconnect app credentials wherever you land.
Run old and new in parallel until you trust the new one.
Do not leave any of this for deadline week.

Relay built a good product and is winding down about as responsibly as a shutdown can be done — clear dates, real exports, refunds. That does not make losing a tool you rely on less disruptive. If we can make the landing easier, the offer above stands through September 14.