Relay.app is shutting down: dates, what to export, and what users should do next

Article type: News / update
Status: Fast-current private publication candidate — Head of Project approval required
Market: Global; Relay publishes its deadlines in Pacific Time
Source check: 9 August 2026
Principal source: Relay.app’s official shutdown announcement and FAQ

Short answer

Relay.app says it is shutting down. Free workspaces are scheduled to close after Saturday, 15 August 2026 at 11:59 p.m. Pacific Time. Paying customers can continue using Relay through Monday, 14 September 2026 at 11:59 p.m. Pacific Time.

Do not wait for the final day. Export your workspace, confirm that the archive opens, document every connection and schedule, and rebuild each important workflow in a replacement system using non-production data before you switch it over.

The dates that matter

Relay says it cancelled paid subscriptions effective 16 July, will make no further charges, and will issue prorated refunds for annual subscriptions. It also says paid customers receive additional monthly steps and AI credits during the wind-down. Check your own workspace and billing record rather than assuming a refund amount.

What you can export

Relay’s export tool creates a ZIP archive. Its FAQ says the archive can include:

• each Workflow, Sequence and MCP Server as JSON;
• the AI prompts associated with those items as Markdown files;
• workflow run history as CSV;
• an exact workflow JSON file and a JSON file for each run; and
• each Relay Table as CSV, where applicable.

Start the full export early. Relay says a workspace export may take up to 24 hours to generate and the emailed download link remains available for 48 hours.

Relay separately says an individual workflow run-history CSV contains up to 100,000 rows per export and is truncated if that workflow has more runs. Relay does not state on this page that the same cap applies to the run-history files inside the full workspace ZIP, so do not generalise the individual-export limit.

An export is a record of your Relay workspace, not a promise that another automation product can import it directly. Relay says its workflow JSON will not work through other builders’ native importers without interpreting the different structure. Treat the archive as migration evidence and a rebuilding reference, not a guaranteed one-click transfer.

What happens to run history, credentials and tokens

Relay says content that is not exported will be deleted when the applicable shutdown window ends. That makes run history important: export it if you may need to investigate failures, prove that an automation ran, or recreate routing logic later.

Relay also says stored credentials and authentication tokens for connected apps will be deleted, after which Relay will no longer be able to access those apps. Credentials are not a substitute for migration documentation. Record which account each connection used, who owns it and what permissions the replacement workflow will need—without copying passwords, private keys or tokens into a document.

A practical migration-preparation checklist

1. Name an owner for every active workflow. If nobody needs a workflow, retire it deliberately instead of migrating it by default.
2. Prioritise by consequence. Move revenue, customer, finance, security and time-sensitive workflows before low-impact convenience automations.
3. Export the workspace now. Follow Relay’s export instructions while the account is still available. Allow up to 24 hours for generation, then save the emailed download within its 48-hour window.
4. Verify the archive. Open the ZIP and check that expected workflow, prompt, run-history and table files are present. Keep an unmodified copy in a controlled location.
5. Document the operating behaviour. For each workflow, record its trigger, schedule, inputs, branches, filters, transformations, destinations, failure notifications and owner.
6. List external dependencies. Record connected apps, service accounts, webhooks, API endpoints and any human approval step. Do not record live secrets.
7. Choose a replacement by operating fit. Consider the team’s technical skill, hosting requirements, governance needs, connector coverage, workload meter and failure-recovery needs. Nerd Mango’s broader automation market guide will address these trade-offs; this shutdown update does not rank alternatives without comparative evidence.
8. Rebuild with synthetic or non-production data. Confirm the business outcome rather than copying Relay’s internal architecture step for step.
9. Test success and failure paths. Check normal runs, missing data, duplicate events, rate limits, retries, partial failures and human escalation.
10. Run a controlled cutover. Where the process allows it, operate the replacement in parallel, compare results, then disable the Relay workflow only after the new route is verified.
11. Preserve the export and decision record. Keep the original archive, migration notes and cutover evidence according to your organisation’s retention and security rules.

If you cannot finish before your deadline

Export first. Then identify any workflow whose interruption could cause customer harm, financial loss, a security problem or a missed legal or operational obligation. Escalate those workflows to the responsible business and technical owners. Do not improvise with unreviewed live credentials or move sensitive data into a personal account.

Relay directs customers with questions to support@relay.app and says technical support remains available during the wind-down, with priority support for paying customers.

What this update does not claim

Nerd Mango has not tested replacement platforms for this article. It does not name a universal “best Relay alternative,” promise that Relay exports import into another product, or guarantee that every workspace receives the same refund or migration support. Those decisions depend on the workflow, plan, region and replacement platform.

Sources

• Relay.app official shutdown announcement and FAQ — retrieved 9 August 2026.
• Relay.app: Export your Relay.app data — linked by Relay’s official shutdown page; retrieved 9 August 2026.

Freshness note

This is a fast-changing shutdown update. Recheck Relay’s official announcement immediately before publication and after either published deadline. Retire or rewrite the deadline-led framing once the shutdown has completed.