Import & Export Flows

Flows can be exported as JSON and imported into any QARK installation. This lets you share flows with teams, back up your library, and migrate between machines.

Export Format

Exported flows use a versioned JSON format:

{
  "version": 1,
  "exported_at": "2025-03-13T10:30:00Z",
  "flows": [
    {
      "title": "Fix Grammar",
      "description": "Correct spelling, grammar, and punctuation errors",
      "content": "Fix all errors in the following text...\n\n{{ input }}",
      "category": "Writing",
      "system_prompt": "You are a meticulous proofreader...",
      "system_prompt_mode": "replace",
      "post_process_template": null,
      "output_action": "paste",
      "preview_mode": "diff",
      "provider_type": "openrouter",
      "model": "x-ai/grok-4.1-fast",
      "temperature": 0.2,
      "max_tokens": 8192,
      "thinking_enabled": false,
      "copy_output": false,
      "enabled_tools": null,
      "agent_ref": null,
      "is_favorite": true,
      "tags": ["writing", "grammar"]
    }
  ]
}

Key fields:

Field	Description
content	The template text with double-brace variables like input, clipboard, etc.
system_prompt	Instructions for the model (separate from content)
system_prompt_mode	"replace" or "append"
output_action	"copy", "paste", "insertBefore", "insertAfter", or "openInChat"
preview_mode	"none", "preview", or "diff"
agent_ref	Agent reference in "@AgentName" format (portable across installations)
enabled_tools	JSON array of tool IDs, may include "agent_tool:@Name" references

Agent references use the @AgentName format instead of UUIDs, making exports portable. QARK resolves these to local agent IDs during import.

Export Flows

• Single flow — Open the flow’s context menu and select Export. Saves a .json file named after the flow.
• Multiple flows — In the flow library, select multiple flows and choose Export Selected. Saves a single .json file with all selected flows.
• All flows — Select Export All from the flow library menu for a complete backup.

Import Flows

Open the flow library and select Import, then choose a .json file. QARK accepts both single-flow and multi-flow JSON formats.

During import, QARK handles:

• Duplicate detection — Flows with matching title and content are skipped to prevent duplicates.
• Agent resolution — @AgentName references in agent_ref and agent_tool:@Name in enabled_tools are resolved to local agent UUIDs. If an agent is not found, the reference is cleared.
• Category creation — If an imported flow references a category that does not exist locally, the category is created automatically.
• Sort order — Imported flows are auto-assigned sort positions after existing flows.

Built-in flows cannot be overwritten by imports.

Duplicate a Flow

Right-click any flow and select Duplicate to create an editable copy with “(Copy)” appended to the title. Use this to:

• Create variations of a working flow (e.g., “Summarize” → “Summarize for Executive Audience”)
• Make a built-in flow editable
• Test changes without modifying the original

The duplicate is independent — editing it does not affect the original.

Manage Your Flow Library

Reorder Within Categories

Drag flows to rearrange their position within a category. The sort order determines the sequence in the flow picker. Place high-frequency flows at the top.

Batch Delete

Select multiple flows and choose Delete Selected. Confirmation is required. Built-in flows are protected and cannot be batch-deleted. Deleted custom flows cannot be recovered unless you have an export backup.

Back up before bulk changes

Export your full flow library before reorganizing or deleting flows in bulk.

Share Flows

Flow JSON files are portable across QARK installations on any platform. When sharing:

• Provider/model fields may need adjustment if the recipient uses different providers or model identifiers
• Agent references resolve by name — the recipient needs agents with matching names for agent_ref to resolve
• Tool references in enabled_tools need matching tools available on the recipient’s installation

For team sharing, store flow exports in a Git repository alongside project code. This tracks changes to system prompts over time and lets the team review flow modifications through pull requests.