Synthetic example · reproducible in the analyzer
A Relay approval workflow, mapped to n8n in one minute.
This is not a customer testimonial. It uses Relay Rescue’s built-in sample—a fictional meeting-briefing workflow—to show exactly what the analyzer finds, what the migration packet proposes, and what still needs human testing.
No real customer dataNo live credentialsRuns in your browserResults shown below are reproducible
What the audit found.
The numbers below come from the same parser and analyzer used for uploaded Relay archives.
What 100 means: the sample contains strong source evidence for planning. It does not mean the rebuilt automation is complete, secure, or behaviorally equivalent.
From Relay evidence to an n8n blueprint.
Relay Rescue preserves the intent and exposes the risky parts. A human still chooses exact nodes, reconnects accounts, and validates behavior.
Relay source evidence
Meeting briefing generator
- TriggerGoogle Calendar · upcoming event
- 01Find company notes · Notion
- 02Draft briefing · OpenAI
- 03Human approval
- 04Send briefing · Gmail
Suggested n8n structure
Rebuild blueprint
- TriggerGoogle Calendar Trigger
- 01Notion search or database query
- 02OpenAI message/model operation
- 03Wait + approval notification/form
- 04Gmail send operation
The useful part is what it refuses to hide.
A diagram is not a migration. The packet calls out the work that cannot be safely inferred from an export.
Check 01
Reconnect credentials deliberately
The sample contains a credential-shaped field. Relay Rescue reports the field name but omits its value. The n8n credential must be created separately with the minimum required access.
Check 02
Rebuild and test approval behavior
The “Human approval” step does not map one-to-one. The owner must choose the approval channel, rejection path, timeout, resumption behavior, and permissions.
| Test | Representative check | Pass condition |
|---|---|---|
| Happy path | Use a meeting with matching Notion notes | Briefing is drafted, approved, and sent once |
| Missing data | Use a meeting without matching notes | Workflow stops or requests input without inventing context |
| Rejection | Reject the generated briefing | No email is sent and the rejection is visible |
| Timeout | Leave the approval unanswered | The workflow follows the chosen timeout policy |
| Duplicate event | Send the same calendar event twice | Recipient does not receive duplicate briefings |
The 60-second walkthrough.
Open the sample alongside this timeline. It is the exact sequence to record for a short product demonstration.
Start with the problem
“Relay is gone. Before rebuilding, I need to know what this workflow actually depended on.”
Open the safe sample
Show the archive summary: one workflow, four detected apps, and two review checks.
Inspect the evidence
Point to steps, run history, build prompt, and apps that must be reconnected.
Show the honest warnings
Highlight credential redaction and the approval behavior that needs explicit testing.
Choose n8n
Show the generated rebuild prompt and the target selector—planning assistance, not automatic conversion.
Close with the value
“The free audit runs locally. Start with your Relay export at relayrescue.app.”
What leaves the browser.
Only files the user explicitly downloads. Relay Rescue does not upload the source archive or generated packet.
Inventory CSV
A sortable list of discovered objects, app dependencies, run evidence, and readiness indicators.
Rebuild brief
A target-specific prompt that preserves known intent, lists unknowns, and requires credential reauthorization.
Structure files
A packet manifest and Mermaid diagrams that make review and handoff easier.
Try the evidence, not the pitch
Reproduce this result in your browser.
Open the built-in sample, inspect every finding, and download the n8n packet. Then replace the sample with your own Relay export when you are ready.
Synthetic demonstration only · no claim of automatic migration or behavioral equivalence.