Relay.app → n8n migration
Relay Rescue turns a Relay workspace export into an inventory, migration-risk audit, and n8n-focused rebuild packet. Your archive stays in the browser, and the result is a plan—not a fake one-click conversion.
Start from evidence in the export, then validate behavior in n8n before switching off the original automation.
Download the full Relay workspace archive and keep an untouched copy as your source record.
Open the ZIP in Relay Rescue to list workflows, sequences, tables, app dependencies, prompts, and missing artifacts.
Use the generated handoff prompt to recreate triggers, nodes, expressions, branches, waits, and credentials.
Run representative inputs, compare outputs, test failures and approval paths, then activate deliberately.
This is a planning map, not an import guarantee. Exact n8n nodes depend on the apps and data each Relay workflow uses.
| Relay concept | Likely n8n building block | What to verify |
|---|---|---|
| Workflow trigger | Trigger node, Webhook, Schedule Trigger, or app trigger | Polling interval, webhook verification, timezone, and duplicate handling |
| App action | App node or HTTP Request node | Credential scope, required fields, pagination, and API limits |
| Paths and conditions | IF or Switch nodes | Fallback branch, empty values, ordering, and merge behavior |
| Wait or approval | Wait node plus the appropriate notification or form pattern | Resume behavior, timeout, permissions, and rejection path |
| Reusable sequence | Sub-workflow or Execute Workflow pattern | Inputs, outputs, error propagation, and version ownership |
| Relay table | n8n data storage or an external database | Schema, row identity, retention, and concurrent updates |
Choose based on operating requirements, not feature-count alone.
Important: Relay's export is not a native n8n workflow file. Relay Rescue produces a structured rebuild packet and redacted prompts; it never claims behavioral equivalence.
The short answers before you start rebuilding.
No. The platforms do not share a native workflow schema. Relay Rescue inventories the source and generates a rebuild plan, but each n8n workflow still needs to be created, reconnected, and tested.
No. The archive is read in the current browser tab. Relay Rescue does not send workspace files, workflow contents, or generated packets to a server.
No. Reconnect every destination credential deliberately and use the least privilege the workflow requires. Credential-shaped values are redacted from generated output.
Start with high-value workflows that have simple control flow and clear owners. Preserve complex approval, branch-heavy, or stateful workflows until the migration pattern is proven.
Run the free local audit first. If you want help with destination fit, risk review, and rebuild order, add the optional $99 migration-planning call. The $99 is credited toward an assisted rebuild if you continue.
support@relayrescue.app · Opens an email draft, not a booking or payment. Include your time zone and destination; do not send exports, credentials, packets, or customer data. No obligation to purchase rebuild services.