> For the complete documentation index, see [llms.txt](https://docs.ixhello.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ixhello.com/ixhc2/technical-specifications/flow-import-export.md).

# 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

<figure><img src="/files/52K1W1chLSGLgSDpGZDm" alt=""><figcaption></figcaption></figure>

* Import flows with validation and conflict resolution

<figure><img src="/files/YGL6hIkpqZuCiKUyGeZW" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/MDEig0omg2i6221IRMwm" alt=""><figcaption></figcaption></figure>

* 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

<figure><img src="/files/5YaDFxKTgwtEhM18yALY" alt=""><figcaption></figcaption></figure>

Advanced Capabilities

* Modify exported flows using LLMs and re-import

<figure><img src="/files/M8qp18FrCiuMFIJzXYBl" alt=""><figcaption></figcaption></figure>

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)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ixhello.com/ixhc2/technical-specifications/flow-import-export.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.