Best starting point
I have the workspace ZIP
Keep an untouched backup. Open a copy in Relay Rescue to inventory workflows, sequences, tables, app dependencies, run evidence, and migration risks.
Audit the ZIP free →Relay.app recovery guide · after shutdown
Relay is unavailable. Your next move depends on what you saved.
Relay Rescue cannot restore a deleted Relay account or retrieve data from Relay. It can help you inspect files you already have, identify what is missing, and turn the surviving evidence into a safer rebuild plan.
No account recovery claimsNo workflow uploadPartial files supported
Start with the evidence you still have.
Do not overwrite, edit, or reorganize the only copy. Preserve the source files first, then work from duplicates.
Partial recovery
I have JSON, CSV, prompts, or screenshots
Collect every Relay file into one folder. Relay Rescue can inspect supported individual files, but missing context should be treated as unknown—not assumed to be safe.
Inspect the files locally →Reconstruction
I have no Relay export
You cannot recreate the original workspace exactly from nothing. Reconstruct business behavior from connected apps, owners, messages, schedules, webhook callers, and logs.
Build a recovery inventory →No export? Reconstruct the behavior, not the old canvas.
The goal is continuity: identify what triggered work, what decisions were made, what changed in each app, and who needed to approve or receive the result.
Look for operational evidence
- Emails, Slack messages, and approval notifications sent by workflows
- CRM, spreadsheet, database, and ticket history with timestamps
- Calendar schedules, webhook callers, forms, and API logs
- Browser history, internal documentation, screenshots, and team notes
- App connections and service accounts previously used by Relay
Write one record per workflow
- Business purpose and accountable owner
- Trigger, schedule, or inbound webhook
- Inputs, conditions, branches, waits, and approvals
- Actions, destinations, expected outputs, and failure alerts
- Representative test cases and acceptable recovery time
Security first: treat old credentials and webhook URLs as potentially exposed or obsolete. Revoke what is no longer needed, create least-privilege replacement credentials, and never paste secrets into migration prompts or public support threads.
Rebuild in risk order.
Do not switch every automation at once. Recover a small, representative workflow first and use it to prove the destination, credential model, and testing process.
Rank the workflows
Start with high-value automations whose owners, inputs, and expected outputs are clear. Flag financial, customer-facing, or compliance-sensitive work for extra review.
Choose a destination
Use n8n for control and flexibility, Make for visual data mapping, or Zapier for straightforward managed automation. Confirm required apps before committing.
Reconnect deliberately
Create fresh credentials with the minimum required permissions. Verify the account, workspace, region, and record ownership behind every connection.
Test before enabling
Run normal, empty, duplicate, alternate-branch, and failure cases. Compare outputs with surviving evidence and add monitoring before activation.
Post-shutdown questions.
Be precise about what can be recovered and what must be rebuilt.
Can Relay Rescue recover my deleted Relay account?
No. Relay Rescue has no access to Relay's systems and cannot restore an account, workspace, credentials, or files that were not saved before deletion.
Can I use Relay Rescue without the complete ZIP?
Yes, supported JSON, CSV, and Markdown files can be opened individually. The result will only reflect the files provided, so missing objects and relationships must be investigated separately.
Will the old Relay webhooks and schedules keep running?
Do not assume they will. Identify every external caller and schedule, replace the endpoint or job, test authentication, and confirm the old path no longer receives production traffic.
Can another platform import the Relay files automatically?
Relay exports are not native n8n, Make, or Zapier projects. Use the surviving structure and build prompts as references, then configure credentials and validate behavior in the destination.
Does Relay Rescue upload my recovered files?
No. File inspection and packet generation happen in the current browser tab. Only payload-free action counts are recorded; file contents and generated packets are not transmitted.
Turn what survived into a rebuild plan.
Run the free local audit first. If the evidence is incomplete or the rebuild order is unclear, the optional $99 planning call covers recovery scope, destination fit, and the safest first workflow.
support@relayrescue.app · Opens an email draft, not a booking or payment. Describe the situation, but do not send exports, credentials, packets, or customer data.