Control and flexibility
n8n
Strong when you need self-hosting, custom APIs, complex branching, reusable sub-workflows, or detailed execution inspection.
Read the n8n guide →Relay.app shutdown · migration checklist
Relay now says its accounts, workflows, and run history have been permanently deleted. Relay Rescue cannot retrieve them. If you saved an export, preserve the original and inspect a copy locally; otherwise reconstruct the most important workflows from connected apps, messages, schedules, and team records.
Check Relay's official shutdown notice ↗
What you can recover depends on what your team saved before Relay closed. Do not assume missing files or workflow behavior can be reconstructed exactly.
Back up any previously downloaded workspace ZIP, individual files, screenshots, emails, and documentation before editing a copy.
List workflow owners, connected accounts, former schedules, webhook callers, and the people who approved human steps.
Use Relay Rescue to inventory saved workflows, sequences, tables, dependencies, prompts, run evidence, and missing artifacts.
Compare operating needs and complexity. One destination does not have to win every workload.
Migrate in value-and-risk order, reconnect credentials, test alternate branches, and keep rollback evidence.
Relay Rescue is not another platform's importer. It creates a neutral inventory and risk assessment so you can choose the right rebuilding environment.
Control and flexibility
Strong when you need self-hosting, custom APIs, complex branching, reusable sub-workflows, or detailed execution inspection.
Read the n8n guide →Visual data mapping
Strong for visual scenarios, routers, iterators, aggregators, and teams that want managed infrastructure.
Read the Make guide →Fast managed setup
Strong for familiar business apps, linear workflows, and teams prioritizing straightforward nontechnical ownership.
Read the Zapier guide →Check official help first: Make and Zapier have published Relay migration guidance. Confirm current eligibility and availability directly with them. Relay Rescue is useful when you have a saved export and want to understand what may not translate cleanly. Make migration guidance ↗ · Zapier migration guide ↗
The packet is a planning artifact, not an automatic conversion. It is designed to make the manual rebuild safer and easier to hand off.
The practical answers before you commit to a destination or consultant.
No. Relay exports are not native n8n, Make, or Zapier imports. Relay Rescue creates an inventory, risk audit, and rebuild packet. Credentials and behavior must be recreated and tested.
Use it when you are eligible and the destination fits your operating needs. Keep the original export and an independent inventory so you can verify scope, omissions, and behavioral differences.
Start with high-value workflows that have clear owners, representative test data, and manageable control flow. Use those to prove your destination pattern before moving complex approvals or stateful automations.
No. The workspace archive is read in the current browser tab. Only payload-free usage signals are sent; workflow contents and generated packets are not transmitted.
Start with a free local audit and migration packet. The optional $9 Automation Rebuild Kit adds an offline workbook, destination checklists, and editable test and rollback templates. No call or subscription.
Optional support is not connected yet.
Do not send exports, credentials, packets, or customer data. The kit is not a working importer or account recovery service.