Workflow Import & Export

Workflows can be exported as self-contained JSON files and imported on any MIRA installation. Exports capture all steps, routing rules, and metadata — no credentials or session data are included.

Exporting a workflow

Open Workflows

Press ⌘3 to open the Workflows view.

Select the workflow

Click the workflow card, then click ⋮ → Export.

Save the file

Choose a location and save as [workflow-name].json.

Importing a workflow

Open Workflows

Press ⌘3.

Click Import

Click the Import button at the top of the workflow list.

Select the JSON file

Pick the .json file. The workflow appears in your list immediately and is ready to run.

Workflow JSON format

The exported JSON mirrors the internal workflow schema exactly. All fields are required unless marked optional.

{
  "name": "My Custom Pipeline",
  "description": "What this workflow does — shown in the workflow card.",
  "trigger": "manual",
  "isEnabled": true,
  "skillId": null,
  "tags": [],
  "steps": [
    {
      "stepOrder": 0,
      "name": "Clarify Scope",
      "description": "Restate the user request clearly before proceeding.",
      "stepType": "prompt",
      "conditionExpr": "",
      "promptTemplate": "Restate the following request in precise, unambiguous terms:\n\n{{input}}",
      "outputFormat": "markdown",
      "onSuccess": "continue",
      "onFailure": "retry:2"
    },
    {
      "stepOrder": 1,
      "name": "Human Review",
      "description": "Pause for the user to review and approve before continuing.",
      "stepType": "human_review",
      "conditionExpr": "",
      "promptTemplate": "",
      "outputFormat": "text",
      "onSuccess": "continue",
      "onFailure": "abort"
    },
    {
      "stepOrder": 2,
      "name": "Format Output",
      "description": "Transform the previous step's output into a final Markdown report.",
      "stepType": "transform",
      "conditionExpr": "",
      "promptTemplate": "Format the following as a structured Markdown report:\n\n{{prev_output}}",
      "outputFormat": "markdown",
      "onSuccess": "continue",
      "onFailure": "skip"
    }
  ]
}

Workflow root fields

Field	Type	Required	Notes
`name`	string	✅	Displayed on the workflow card
`description`	string	✅	One-line summary
`trigger`	string	✅	`"manual"` (user starts it) or `"auto"` (starts with session)
`isEnabled`	boolean	✅	`true` to make the workflow selectable
`skillId`	string \| null	✅	ID of a skill to activate automatically when this workflow runs, or `null`
`tags`	string[]	✅	User-defined labels for filtering. Use `[]` for none.
`steps`	Step[]	✅	Ordered array of steps — executed top to bottom by `stepOrder`

Step fields

Field	Type	Required	Notes
`stepOrder`	number	✅	Zero-based execution order. Must be sequential: 0, 1, 2, …
`name`	string	✅	Short label shown in the workflow progress bar
`description`	string	✅	Longer explanation of what this step does
`stepType`	string	✅	See valid values below
`conditionExpr`	string	✅	Natural-language condition for `condition` steps. Leave `""` for other types.
`promptTemplate`	string	✅	The prompt sent to the LLM. Use template variables (see below). Leave `""` for `human_review`.
`outputFormat`	string	✅	See valid values below
`onSuccess`	string	✅	What to do when the step succeeds
`onFailure`	string	✅	What to do when the step fails

stepType valid values:

"prompt" — send promptTemplate to the LLM and collect output
"transform" — reshape or reformat the previous step’s output
"condition" — evaluate conditionExpr; routes based on result
"human_review" — pause execution and wait for the user to approve before continuing

outputFormat valid values: "text" · "markdown" · "json" · "code" · "table" onSuccess valid values: "continue" · "pause" onFailure valid values: "retry:1" · "retry:2" · "retry:3" · "skip" · "abort"

Template variables

Variable	Resolves to
`{{input}}`	The original user message that started the workflow
`{{prev_output}}`	The full output of the immediately preceding step
`{{document}}`	The content of any document attached to the session

Version history

MIRA saves a new version each time you save a workflow. To access version history:

Open the workflow editor.
Click ⋮ → Version History.
Browse versions by timestamp.
Click Restore to roll back — this creates a new version entry rather than overwriting the history.

Distributing workflows to your team

Export the workflow JSON.
Commit the file to your team’s shared repository.
Each team member imports the file into their MIRA installation.

Because workflows reference only template variables (not local paths or credentials), the same JSON runs identically on any machine.

Edit this page — Open a pull request

Get Started

Core Concepts

Features

Eval Framework

Configuration

Developer Guide

Community

Reference

Workflow Import & Export

Exporting a workflow

Importing a workflow

Workflow JSON format

Workflow root fields

Step fields

Template variables

Version history

Distributing workflows to your team

​Exporting a workflow

​Importing a workflow

​Workflow JSON format

​Workflow root fields

​Step fields

​Template variables

​Version history

​Distributing workflows to your team

Exporting a workflow

Importing a workflow

Workflow JSON format

Workflow root fields

Step fields

Template variables

Version history

Distributing workflows to your team