RRRelay Rescue

Relay.app export recovery · after shutdown

Already saved an export? Preserve it and inspect a copy.

Relay now says all accounts, workflows, and run history have been permanently deleted. This page is for people who saved a workspace ZIP or individual files before shutdown; Relay Rescue cannot request a new export or restore deleted data.

Inspect saved files locally No export? Open the recovery guide →
Saved files onlyKeep an untouched ZIPNo Relay data uploaded here

Preserve what you saved.

A previously downloaded workspace ZIP is the broadest surviving record of what you built. Expired email download links may no longer work; do not assume Relay can generate another archive.

  1. Find existing copies

    Check your Downloads folder, shared drives, backups, and the inbox where Relay sent export notices for a ZIP already saved locally.

  2. Keep an untouched original

    Copy the archive to a backed-up location. Work only from duplicates, and record which workspace each file came from.

  3. Collect other evidence

    Bring together saved screenshots, individual JSON or CSV files, build prompts, team notes, and connected-app logs.

  4. Inspect before rebuilding

    Inventory the surviving files before choosing a destination, and mark missing objects or behavior as unknown.

Know what may be inside.

Relay documented a folder for each Workflow, Sequence, MCP Server, and Table. Use this as a completeness check for an export saved before shutdown.

Included in the workspace ZIP

  • Build prompts in Markdown
  • Workflow structure in JSON
  • Run history in CSV
  • Individual run records in JSON
  • Table data in CSV where applicable

Evidence outside the ZIP

  • Workflow screenshots for visual layout
  • Workflow owners and approvers
  • Schedules and external webhook callers
  • Connected account names and credential owners
  • Expected outputs and failure behavior

Screenshots were separate. Relay said workflow screenshots were not included in the workspace export. Look for screenshots previously saved by your team; they cannot be recovered from the ZIP if they were never captured.

Check the export without uploading it.

Relay Rescue reads the ZIP in your browser and creates an inventory, risk assessment, and rebuild packet for n8n, Make, or Zapier. It does not automatically convert or deploy workflows.

Step 1

Confirm coverage

Check that expected workflows, sequences, MCP servers, tables, and run evidence appear in the inventory.

Step 2

Find migration risks

Review branches, approvals, webhooks, AI steps, waits, credentials, and missing artifacts before choosing a rebuild order.

Step 3

Generate a handoff

Create a target-specific packet with an audit, diagrams, inventory CSV, and implementation prompts.

Saved-export questions.

What the files can and cannot tell you after shutdown.

Can I import Relay's JSON directly into another platform?

Relay says other workflow builders use different JSON structures, so the file will not work through their native importers. Use the exported build prompt and JSON as rebuilding references.

Are connected app credentials included?

No. Plan to create fresh, least-privilege connections in the replacement platform, and never share secrets in migration prompts.

Can I still request a new export?

Relay's official site says accounts, workflows, and run history have been permanently deleted. Relay Rescue cannot retrieve them. If you have no saved export, use the post-shutdown recovery guide to reconstruct behavior from other records.

Does Relay Rescue upload the ZIP?

No. The archive is processed in the current browser tab. The site records only payload-free action counts; workflow contents and generated packets are not transmitted.

Turn the saved export into a migration plan.

Keep the original ZIP untouched. Open a copy in the free analyzer to verify coverage and produce a rebuild packet before reconnecting apps.

Audit the Relay export freeNo saved export?