RRRelay Rescue

Relay.app export guide · September 2026

Save the workspace before the window closes.

Relay says paid accounts and their data will be deleted after September 14, 2026. A full export can take up to 24 hours to prepare, and its emailed download link remains available for 48 hours. Start the export now, then preserve the visual and operational details the ZIP does not capture by itself.

Open Relay workspace settings ↗ Read Relay's official instructions ↗
Official export firstKeep an untouched ZIPNo Relay data uploaded here

Export the complete workspace.

Relay's documented workspace export is the broadest record of what you built. You need workspace access while the export is generated and when the email arrives.

  1. Open workspace settings

    In the Relay dashboard, select Export workspace data. Confirm that you are exporting the correct workspace.

  2. Wait for the email

    Large workspaces may take up to 24 hours. Watch the inbox associated with your Relay account.

  3. Download within 48 hours

    The emailed link expires after 48 hours. Save the ZIP promptly and keep an untouched backup copy.

  4. Inspect before rebuilding

    Inventory the archive before choosing a destination so missing objects or evidence are discovered while Relay is still accessible.

Know what should be inside.

Relay documents a folder for each Workflow, Sequence, MCP Server, and Table. Use this as a quick completeness check after downloading.

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

Capture separately

  • 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 require a separate action. Relay says workflow screenshots are not included in the workspace export. Open each important workflow and use Save workflow as screenshot while the workspace is still available.

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.

Relay export questions.

Details worth checking while access remains available.

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. Relay says stored app credentials and authentication tokens will be deleted at the end of the wind-down period. Plan to reconnect each app in the replacement platform.

Should I export individual workflows too?

The full workspace ZIP already includes individual workflow data. An additional individual export can be useful for a critical workflow, but it should not replace the complete workspace export.

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 freeWhat if Relay is unavailable?