Flow Import / Export

Overview

Flow Import/Export enables portability and reuse of flows across environments. It allows flows to be packaged, transferred, versioned, and reconfigured easily.

Key Benefits

• Environment Portability: Move flows across Dev, QA, and Prod

• Version Control: Maintain versions of flow definitions

• Reusability: Duplicate and customize flows efficiently

• Automation Ready: Enables LLM-driven flow modification

Core Capabilities

• Export flows as YAML-based YFlow files

• Import flows with validation and conflict resolution

• Customize flows during import

Export Contents

• Flow definitions

• Nodes and logic

• Persona and configurations

• Integrations (e.g., REST APIs)

Import Features

• Drag-and-drop upload

• Automatic validation

• Conflict detection across:

  • Flow logic

  • Persona settings

  • Integrations

• Options to:

  • Override existing flows

  • Retain existing configurations

Advanced Capabilities

• Modify exported flows using LLMs and re-import

Step by step guide:

Step 1: Export the Flow

• Navigate to the flow in the platform

• Use the Export option to download the flow as a YFlow (YAML) file

Step 2: Prepare the Flow for Editing

• Open the exported YFlow file in:

• Text editor (VS Code, Notepad++)

• LLM interface (ChatGPT, Copilot, etc.)

• Identify sections to modify:

Step 3: Use LLM to Modify the Flow

• Provide the YFlow content to an LLM with clear instructions.

• Example prompts:

  • “Add error handling to all API nodes”

  • “Insert a new node after greeting to validate user input”

Step 4: Validate the Modified File and Re-import the Flow

• Go to the target environment (Dev / QA / Prod)

• Use the Import feature

• Upload the modified YFlow file

Step 5: Resolve Conflicts

• During import:

  • The system detects differences between:

  • Existing flow

    • Imported flow

You can:

• Override existing configurations

• Retain current version

• Selectively apply changes (persona, integrations)

This feature forms foundation for:

• Blueprints: as they are productized and cataloged imports of exported flow definitions.

• Reusable templates: as they can be broken down and reused across multiple implementations.

• Automated deployment workflows

Notes / Limitations

• Does not include Knowledge Bases (since they may contain external document data and indexed content rather than simple text-based configuration.)

• Does not include widgets (since they are structurally different from standard flow components)

• API-based automation not exposed yet (may be considered in future road map)