Skip to content
Rival Docs

Importing & Exporting Workflows

Overview

A workflow can be exported as a single portable JSON file and imported into any other Rival workspace. The file carries the workflow’s design - its name, description, tags, and the full graph of steps and connections. It never carries API keys or connected accounts - whoever imports it connects their own.

Both actions live on My Tools (/my-tools).

Exporting a workflow

  1. On My Tools, open the ⋯ menu on the workflow’s card and choose Export.

  2. The Export workflow dialog shows a preview of the JSON. Click Download to save it as Name.workflow.json, or Copy JSON to put it on the clipboard.

Export is offered to anyone who can open the workflow with Editor access - its creator, an org Owner or Admin, or an Editor on a team that holds it. Executors on a team can run the workflow but don’t see Export: being allowed to run a workflow is not being allowed to walk off with how it works. You also need an active seat.

An adopted workflow whose graph the publisher locked can’t be exported, for the same reason it can’t be opened in the builder.

What the file contains

  • Name, description, avatar, and tags
  • The graph - every step, its settings, and the connections between them
  • A manifest of everything the graph points at: tools, connectors, agents, and sub-workflows

What is never included

  • API keys on model steps. Any step that carried its own key is switched to the platform model, and the key is stripped.
  • Connected accounts for connector steps
  • Run history

Importing a workflow

  1. On My Tools, click Create, hover over New Workflow, and click the Import chip that appears beside it.

  2. In the Import a workflow dialog, click Choose a .json file, or paste the JSON into the text box.

  3. Click Import. The workflow is created and opened for you, with a summary of any steps that need attention.

Importing always creates a new workflow - nothing existing is overwritten. If a workflow with the same name already exists, the import is named Name (2), and you’re told so. Any member with an active seat can import.

After the import

Each step that points outside the workflow is checked against your workspace:

Step points atResolves when
A tool or connectorIt’s public on the marketplace, or belongs to your organization
An agentIt belongs to your organization, or has a public listing
A sub-workflowIt belongs to your organization. A published workflow has to be adopted first

Steps that don’t resolve are listed under Steps to fix. The workflow is still created; open each flagged step and pick something your workspace has. The summary also reminds you that:

  • Connector steps need connecting in your workspace.
  • Model steps came in on the platform model, since API keys are never exported. Choose your own key on each one if you want it back.

Next steps