Import & Export

The Import and Export tools allow you to save your conversational flows as JSON files and load them back into the builder. This is useful for backups, sharing flows between environments, or migrating flows.

Accessing Import/Export

1. Click the Settings button (gear icon) in the top bar
2. Navigate to the General tab
3. Find the Export and Import buttons

Exporting a Flow

How to Export

1. Open the Settings menu
2. Go to the General tab
3. Click the Export button (download icon)
4. The file will download automatically

Export File Details

The exported JSON file contains:

File Naming

The exported file follows this naming convention:

{alias}-v{version}-{timestamp}.json

Example: onboarding-flow-v3-1705678900000.json

Importing a Flow

How to Import

1. Open the Settings menu
2. Go to the General tab
3. Click the Import button (upload icon)
4. Select a JSON file from your computer
5. Review the confirmation dialog
6. Click Confirm to import

What Gets Imported

When you import a flow, the following elements are updated:

1. Nodes and Edges - The entire flow structure is replaced
2. Variables - All flow variables are updated
3. Web Configuration - Chatbot appearance settings are applied

Import Confirmation

Before importing, a confirmation dialog appears warning that:

• Current flow content will be replaced
• This action cannot be undone
• It's recommended to export the current flow first as backup

Importing Variables from Another Flow

Flows that hand customers to each other usually share variables: the identity a login flow saves, the amount an onboarding flow asks for. Instead of declaring them again by hand in every flow, you can bring them over from a flow that already has them. This imports only the variable declarations, not nodes or values, and it does not replace anything.

1. Open the flow's Variables panel and click Import from another flow. The button is only in the conversational flow editor, not in the Forms Builder.
2. Select the source flow. The list shows the tenant's flows except hidden ones and the flow you are editing.
3. The dialog lists the variables declared in that flow, all checked by default. Uncheck the ones you do not want. Each row tells you whether the variable Already exists in this flow, or whether it is a Conflict because this flow declares it with another data type.
4. Click Import.

The merge follows three rules:

A message sums up the result, for example Imported: 4. Skipped because they already existed: 2. Type conflicts: 1., and it shows as a warning when there was any conflict. The variables are saved the same way as when you add one by hand, so if someone else changed the flow in the meantime you get the same version-conflict notice and the current version is reloaded.

Use Cases

Backup Before Major Changes

Before making significant modifications to your flow:

1. Export the current version
2. Make your changes
3. If something goes wrong, import the backup

Environment Migration

To move a flow from staging to production:

1. Export from staging environment
2. Import into production environment
3. Adjust any environment-specific configurations

Team Collaboration

Share flows with team members:

1. Export your flow
2. Share the JSON file
3. Team member imports into their workspace

Version Control

Keep historical versions of your flows:

1. Export after each major milestone
2. Name files descriptively
3. Store in your version control system

File Format

The exported JSON has the following structure:

{
  "label": "Flow Name",
  "alias": "flow-name",
  "description": "Flow description",
  "nodes": [...],
  "edges": [...],
  "variables": [...],
  "webConfiguration": {
    "logo": "...",
    "displayName": "...",
    "description": "...",
    "avatar": "...",
    "primaryColor": "#...",
    "buttonText": "..."
  },
  "exportedAt": "2024-01-19T12:00:00.000Z",
  "exportVersion": "1.0"
}

Troubleshooting

Import fails with error

Check that:

• The file is valid JSON
• The file contains nodes and edges arrays
• The file was exported from a compatible version

Some settings are not imported

Web configuration (logo, avatar, colors) is imported separately. If these don't appear:

• Check that the webConfiguration object exists in the file
• Refresh the page after import

Nodes appear but connections are missing

This can happen if:

• The file was manually edited and edge references are invalid
• The export was from an incompatible version

Try re-exporting from the original source.