How to Migrate from Relay.app to n8n or Zapier in 48 Hours (2026 Guide)

Relay.app Is Closing. Move in 48 Hours.

A Relay migration means rebuilding its triggers, agents, approvals, and controls on another platform. Relay's JSON files keep workflow details. They won't recreate a working system on their own.

StoryPros recommends n8n for control and Zapier for speed.

Step 1: Export Everything in the First 4 Hours

Relay sent its shutdown notice on July 16, 2026. According to Inbox Zero, free accounts close August 15 at 11:59 p.m. PT.

Paid accounts close September 14 at 11:59 p.m. PT. Relay says it will permanently delete account data after each deadline.

Download these files first:

• Workflows, Sequences, and MCP servers as JSON
• Every AI prompt
• Workflow run history
• Relay Tables as CSV
• Screenshots of approval steps
• Screenshots of app connections
• One successful run for each workflow
• One failed run for each workflow

Store two copies outside Relay. Put one in company-owned storage, such as Google Drive, SharePoint, or Amazon S3.

Relay's export won't keep working OAuth access. You'll need to reconnect Google, HubSpot, Salesforce, Slack, and other apps.

Next, create a migration manifest. Use one row per workflow.

Field	What to record
Workflow name	Exact Relay name
Owner	Person responsible after migration
Business purpose	Lead routing, proposal approval, renewal alert
Trigger	Webhook, schedule, CRM event, form
Inputs	Required fields and formats
Branches	Every filter and decision
AI prompt	Full system and user instructions
Approval	Approver, timeout, rejection path
Destination	CRM, Slack, email, database
Monthly runs	Actual volume from Relay history
Failure alert	Channel and owner
Test record	Known input with expected output

Don't treat inactive workflows as trash. Old workflows often contain useful prompts and field mappings.

Expected outcome: You own the workflow logic, prompts, tables, and run records.

Step 2: Choose n8n or Zapier by Hour 8

Relay called its workflows "AI teammates." The label made them sound simple.

Underneath, they were triggers, conditions, API calls, model prompts, and approval gates. Calling them agents didn't reduce vendor risk.

Agent-first no-code tools can hide how dependent your process is on one vendor.

This isn't a new lesson.

Facebook announced Parse's shutdown in January 2016. It gave developers one year and released Parse Server for self-hosting. Relay users get 30 days on free accounts and 60 days on paid accounts.

Choose based on who will own the workflows.

Requirement	Pick n8n	Pick Zapier
Fast setup for common apps		✓
Nontechnical workflow owner		✓
Self-hosting	✓
Custom JavaScript or API logic	✓
Detailed branching	✓
Simple CRM and email flows		✓
Lower software cost at high volume	✓
Huge app directory		✓
Portable workflow JSON	✓
Minimal maintenance		✓

n8n Community Edition has a $0 software price. You still pay for hosting, backups, security, and maintenance.

Zapier has a $0 testing plan. Paid costs rise with successful action tasks. Calculate usage before moving high-volume workflows.

At StoryPros, we use n8n instead of Zapier for serious AI workflows. n8n gives us more control over logic, errors, APIs, and model costs.

Zapier works well when you need a HubSpot-to-Slack workflow this afternoon. Use n8n when that workflow controls revenue.

Expected outcome: Every workflow has a target platform and a named owner.

Step 3: Map Relay's Parts by Hour 20

Don't rebuild by copying screenshots step by step. Rebuild the business rules.

A 2026 study examined more than 6,000 public n8n workflows. It found that few had explicit fallbacks, repair loops, alerts, or approval gates.

That is the main migration risk. The happy path is easy to rebuild.

Use this map:

Relay primitive	n8n equivalent	Zapier equivalent
App trigger	App Trigger node	Zap trigger
Schedule	Schedule Trigger	Schedule by Zapier
Webhook	Webhook node	Webhooks by Zapier
Filter	Filter or If node	Filter by Zapier
Branch	Switch node	Paths
AI agent	AI Agent or LLM Chain	AI by Zapier action
Tool call	App node or HTTP Request	App action or webhook
Table	Data Table or Postgres	Zapier Tables
Human approval	Wait node plus approval webhook	Human in the Loop step
Error path	Error Trigger workflow	Error handler and alert Zap
Run history	Execution data plus external log	Zap History plus external log

Keep AI prompts outside visual workflow labels. Store the full prompt, model name, response format, and version.

Use a strict output format. A lead-scoring step should return defined fields such as `score`, `reason`, and `route`.

Don't let an AI step send customer email without a gate. Put approval before the Gmail, Outlook, or HubSpot action.

Every approval needs five fields:

1. Execution ID 2. Approver identity 3. Decision 4. Timestamp 5. Approved content hash

A Slack thumbs-up isn't an audit record. Save the decision in Postgres, Airtable, Zapier Tables, or your CRM.

Expected outcome: Each Relay step has a named replacement and written failure behavior.

Step 4: Rebuild Controls by Hour 36

Relay JSON won't import directly into n8n. The platforms use different node names, credentials, schemas, and connection rules.

Treat Relay's JSON as a specification. It is evidence, not an installer.

For n8n, build one clean workflow first. Export it from n8n and reuse it as your internal template.

A reusable n8n template should include:

• Trigger
• Input validation
• Idempotency check
• Main workflow
• Approval gate
• Final action
• Audit-log write
• Error Trigger
• Slack or email alert
• Cost-log write

To import a prebuilt n8n JSON file, open the workflow menu. Choose Import from File or Import from URL.

Self-hosted n8n users can also run `n8n import:workflow --input=workflow.json`. Reconnect every credential before you activate the workflow.

Zapier doesn't accept Relay workflow JSON. Rebuild each Zap from the migration manifest.

Keep approvals in an explicit pending state. Set a timeout for every workflow execution.

Use this approval pattern:

1. Create a pending approval record. 2. Send the approver a unique link. 3. Record the approval or rejection. 4. Resume the workflow through a webhook. 5. Expire the request after its deadline. 6. Alert the workflow owner when it times out.

Add idempotency before any costly or customer-facing action. Use the CRM record ID plus workflow version as the key.

If that key already exists, stop the run. This prevents duplicate emails, deals, and Slack alerts during retries.

Cost controls need their own record:

• Workflow ID
• Execution ID
• Model provider
• Model name
• Input tokens
• Output tokens
• Provider-reported charge
• Paid app actions
• Approval status
• Final result

n8n usually meters cloud plans by workflow executions. Zapier meters many successful action steps as tasks.

The pricing models charge for different workflow shapes. Calculate both before you choose a platform.

Expected outcome: Your replacement has approvals, duplicate protection, logs, and cost records before launch.

Step 5: Shadow Run and Switch by Hour 48

Never switch a revenue workflow after one successful test. Run Relay and the replacement at the same time.

Keep the old workflow as the system of action during testing. Run the new workflow in shadow mode.

Disable customer-facing actions in the new workflow. Write its planned actions to a test table instead.

Compare at least these outputs:

• Number of records received
• Number rejected by validation
• Branch selected
• AI response structure
• Approval request created
• Final destination
• Cost per run
• Error count

Use one known successful Relay run and one failed run. Add one duplicate record and one record with a missing field.

The new workflow passes when both systems make the same business decision. The text does not need to match.

AI wording can change between runs. Routing, approval, and action rules should not.

Switch triggers only after the shadow results match. Keep Relay available for rollback until the cutoff date.

Your final cutover checklist:

• [ ] Relay exports stored in two locations
• [ ] OAuth connections recreated
• [ ] Secrets stored outside workflow code
• [ ] Approval identity recorded
• [ ] Rejection and timeout paths tested
• [ ] Execution IDs written to an external log
• [ ] Duplicate protection tested
• [ ] Model and task costs recorded
• [ ] Failure alerts delivered
• [ ] Workflow owner named
• [ ] Rollback steps documented
• [ ] Relay trigger disabled after cutover

StackGen reviewed nearly 178,000 public status records across more than 390 companies. AI-related incidents caused over 10% of reported outages.

Nine documented cases involved agents damaging live systems or deleting data. Use AI with controls around it.

StoryPros builds AI agents that work under real sales and marketing pressure. We build in approvals, logs, limits, and rollback plans.

A clever prompt will not run your business safely.

FAQ

Is Relay.app comparable to n8n?

Relay.app and n8n both run multi-step workflows with triggers, AI, app actions, and branching. n8n supports self-hosting, custom code, workflow JSON exports, and more control over failures.

What's the difference between Zapier and Relay.app?

Zapier focuses on app-to-app workflows and has a large integration directory. Relay packaged workflows as AI agents and put more focus on built-in human approval.

Is Zapier easier to use than n8n?

Zapier is usually easier for simple workflows and nontechnical owners. n8n takes longer to learn, but it gives you more control over APIs, branching, retries, and AI costs.

How do you import a prebuilt workflow JSON into n8n?

Open an n8n workflow and select Import from File or Import from URL. You can't import a Relay JSON export directly because Relay and n8n use different workflow schemas.

How do you preserve approvals and audit logs during migration?

Create a permanent approval record with the execution ID, approver, decision, timestamp, and content hash. Store run records outside n8n or Zapier when retention and audits matter.

How do you migrate from Zapier to n8n later?

Document each trigger, action, filter, path, credential, and test record before rebuilding it in n8n. Export the finished n8n workflow as JSON. Store that file with your runbook and prompt versions.

Related Reading

• How to Make Any n8n Template Production-Safe in 48 Hours (2026 Guide)
• How to Build One AI Pipeline for Marketing and Ops (2026 Guide)
• AI Agents Need Workflow Engines, Not Better Frameworks (2026)