Export your data from Relay.app
Deadlines first: free accounts and their data are permanently deleted after Saturday, August 15, 2026 at 23:59 PT; paid accounts after Monday, September 14, 2026 at 23:59 PT. The export itself has two timing quirks: generation can take up to 24 hours, and the emailed download link expires 48 hours after it arrives.
- In Relay, open your dashboard and choose Export workspace data.
- Wait for the email (up to 24 hours for large workspaces).
- Download the zip within 48 hours and store it somewhere durable.
- If workflow layouts matter to you visually, screenshot them in the editor; screenshots are not in the zip.
What is in the export
The zip has one folder per workflow, sequence, MCP server, and table. Per workflow:
- prompt.md: a plain-language description of what the workflow does. This is your primary migration artifact.
- workflow.json: the exact structure. No tool imports it natively; treat it as reference detail behind prompt.md.
- Run history CSV (up to 100,000 rows) and a JSON per run: real inputs and outputs, useful for verifying the rebuild against reality.
- Table CSVs: any Relay tables, as spreadsheets.
Credentials and OAuth tokens are never exported; you will re-authenticate every integration wherever you land.
Rebuild each workflow type in flo.space
flo.space does not have workflows to build. You connect tools, and the AI proposes prepared actions that wait for approval. Migrating therefore means checking, per Relay workflow, that the equivalent prepared action shows up and looks right.
| Relay workflow type | What to do in flo.space | Notes |
|---|---|---|
| Email drafting or follow-up (Gmail/Outlook trigger) | Connect the mailbox; the queue proposes replies and follow-ups | Compare drafts against your Relay run history |
| Invoice creation or chasing (QuickBooks) | Connect QuickBooks; invoice drafts and overdue nudges appear as actions | Amounts and terms come from your books |
| Payment links or refunds (Stripe) | Connect Stripe; payment actions are prepared and flagged by risk | High amounts always read as high risk |
| Order or inventory updates (Shopify/ShipStation) | Connect the store; status replies and update actions are proposed | |
| CRM updates (HubSpot/Salesforce) | Connect the CRM; record updates and logged activity are prepared | |
| Approval steps anywhere | Nothing to rebuild; every action waits for approval | This is the default, not a setting |
| Branching pipelines, custom webhooks, unsupported apps | Keep in a workflow builder (Zapier, Make, n8n) | flo.space is deliberately not that tool |
Connect the same integrations
Supported: Gmail, Outlook, QuickBooks, Stripe, Shopify, Slack, HubSpot, Salesforce, Google Drive, Google Sheets, ShipStation, Twilio, DocuSign, and LinkedIn; details per tool live on the integrations pages. Connections start read only. Practical order: connect the mailbox first (most context lives there), then the financial tools, then the rest.
Verify it works before you switch off
- Run flo.space read only for several days alongside your remaining Relay window.
- Pick three real cases from your Relay run history CSVs and confirm the queue proposed the equivalent action with the right data.
- Approve one low-risk action end to end and check the result in the target tool.
- Only then stop relying on the Relay workflow, and revoke Relay's access in each app's security settings.
Troubleshooting
An expected action is not appearing
Check the source tool is connected and that the triggering context is recent; the queue proposes from live context, not historical backfill. If the Relay workflow ran on old data, recreate the situation with a current example.
The draft is right, but the details are wrong
Edit it in plain language before approving ("use the net 30 terms", "make it shorter"). Repeated corrections are worth raising in onboarding; that is what the early access feedback loop is for.
A workflow has no equivalent here
Then it belongs in a builder, and the honest move is to put it there. The four-way comparison shows which one fits which workflow.
Migration deadline pressure
Only the export is deadline-bound. With the zip downloaded, everything on this page can happen after Relay is gone. If you are stuck, contact us and mention Relay.
Work through it with us
Early access onboarding includes a working session for Relay migrations. Bring your export; we map it together, and nothing sends until you approve it.