Relay.app wind-down · paid accounts close Sep 14, 2026

Relay handed you a build prompt. Falcon takes it as input.

Relay's export generates a plain-language description of every workflow you own, because no other platform ingests Relay's JSON. Falcon Builder was built around that exact input. Paste the prompt, review the nodes it proposes, confirm, and run it on a real canvas.

No card required to rebuild and test.
Relay export · build prompt.md
# Workflow: Inbound lead triage
Trigger: new form submission
Step 1: AI extracts company,
  role, and intent from the note
Step 2: if intent = "demo",
  route to sales, else nurture
Step 3: create CRM contact
Step 4: notify #sales channel
Falcon Builder · proposed nodesreview · confirm
webhookForm intake
ai-promptExtract fields
conditionIntent router
http-requestCreate contact
slackNotify #sales
Time remaining · Relay paid workspaces
--days
--hrs
--min
--sec

Sep 14, 2026 · 23:59 PT. After that, Relay accounts and all associated data are permanently deleted, including stored credentials and tokens.

WHAT YOU ACTUALLY GOT

The export is a rebuild aid, not a portable file.

Relay's ZIP contains three kinds of material. Only one of them travels well, and it's the one most people skip.

Structure JSON

Doesn't import anywhere

Every builder models nodes differently. Relay says so directly: the JSON won't work through another tool's native importer. Keep it for reference.

Build prompt · .md

The one that matters

A plain-language spec of the trigger, the steps, the branching, and the AI instructions. Save one for every workflow you care about. This is your migration payload.

Run history · CSV

Your proof of correct

Past runs are the test fixtures for the rebuild. Replay a handful through the new workflow and diff the output before you cut over.

THE SEQUENCE

Four moves, in this order.

Order matters here. Credentials are deleted with the account, so anything that depends on a live Relay connection has to happen before the cutoff, not after. For the full walkthrough — dates, export contents, and an honest comparison of destinations — read the migration guide.

01

Export the full workspace today

Relay's export can take up to 24 hours to generate and the download link expires 48 hours after it lands in your inbox. Export queues get slower as the deadline approaches. Do this first, optimize later.

02

Rank workflows by what breaks if they stop

Revenue, customer response, billing, access provisioning, and time-sensitive alerts go first. Most workspaces have three or four that genuinely cannot fail and a long tail that can wait or die.

03

Paste each build prompt into the importer

Open falconbuilder.dev/import, paste the prompt, and Falcon proposes the workflow. You see every node it mapped before anything is created, and anything it couldn't map is flagged on the canvas — never silently dropped. Confirm, and you're editing a real workflow, not accepting a black box.

04

Reconnect credentials and run both in parallel

Every integration needs fresh OAuth regardless of where you land. Run Falcon alongside Relay while you still have both, replay historical runs from the CSV, and compare outputs node by node in the execution log before you switch the trigger over.

TWO WAYS THROUGH

Rebuild it yourself, or have us do it with you.

Some teams have an operator who knows the workflows and a few free evenings. Some have workflows that can't wait for one. Pick the lane that fits your calendar — both end with a workspace you own.

Do it yourself · Falcon Builder

Rebuild it yourself

For teams with an operator who knows the workflows and has a few evenings.

  • Paste build prompts, review proposed nodes, apply what fits
  • 30+ node types, webhook / schedule / email / SMS / voice triggers
  • OpenAI, Anthropic, Gemini, Mistral, OpenRouter, and Ollama
  • Per-node execution logs with timestamps and payloads
  • Bring your own LLM key and generate without touching platform credits

Free tier to rebuild and test · Pro $29/mo · Business $249/mo

Create a workspace
Done for you · Migration service

Hand over the ZIP

For teams whose Relay workflows are load-bearing and whose calendar is already full.

  • Start on Pro and we'll migrate your first three workflows free — with you, on a call, same week
  • Send us the export; get back working workflows in your own Falcon workspace
  • Credential reconnection and trigger cutover handled with you on the call
  • Historical runs replayed and diffed against the originals
  • Larger workspaces: fixed scope, quoted after a 20-minute review
  • You own the workspace and the workflows on day one

First 3 workflows free with Pro · capacity is limited before Sep 14

Book a 20-minute review
ON LOCK-IN

You just learned what an export policy is worth.

Relay handled its wind-down well — full export, prorated refunds, sixty days of runway. The lesson isn't that automation platforms are risky. It's that you should know the exit before you build the thing you depend on. So here's ours, in writing, before you owe us anything.

Your workflows, readable

Every workflow is structured JSON you can read and take with you — the full definition, nodes, edges, and configs, available through the workflow API on every tier, including free.

Your models

Connect your own OpenAI, Anthropic, Google, or Ollama key. We don't resell tokens or mark up inference — the AI Generator credits model covers generation, and BYOK costs you nothing on the platform.

Your logic, visible

Workflows are a canvas of typed nodes with per-node logs, not an opaque agent. You can read what runs, and so can the next person who inherits it.

Next step

Start with the one that would hurt most.

Pick your highest-stakes Relay workflow, open its build prompt, and paste it in. If it doesn't come back close enough to run, tell us — that's the fastest feedback we can get.

Paste your first promptBook a migration callBusiness-critical workspace? Say so and we'll schedule same week.