Import & Export

Overview

Record Flow allows you to export your flows and workspaces as JSON files. These files can be:

• Shared with team members or the community
• Used as backups for your automation workflows
• Transferred between different installations
• Version controlled using Git or other systems
• Modified manually for advanced use cases

Exporting Flows

Export a Single Flow

To export an individual flow:

1. Open the workspace containing the flow you want to export
2. Right-click on the flow in the flows list
3. Select "Export Flow" from the context menu
4. Choose a location and filename for the JSON file
5. Click Save

Export Multiple Flows

To export multiple flows at once:

1. Open the workspace
2. Select multiple flows by holding Ctrl (Windows/Linux) or Cmd (Mac) and clicking each flow
3. Right-click on one of the selected flows
4. Select "Export Selected Flows"
5. Choose a location and base filename
6. Each flow will be saved as a separate JSON file

{
  "name": "Login Flow",
  "description": "Automated login process",
  "browser": "chrome",
  "variables": [
    {
      "name": "username",
      "value": "user@example.com",
      "scope": "flow"
    }
  ],
  "actions": [
    {
      "type": "navigate",
      "url": "https://example.com/login",
      "order": 1
    },
    {
      "type": "input",
      "selector": "#email",
      "text": "{username}",
      "order": 2
    }
  ],
  "createdAt": "2025-12-05T10:30:00.000Z",
  "updatedAt": "2025-12-05T10:35:00.000Z"
}

Importing Flows

Import a Flow

To import a flow into a workspace:

1. Open the workspace where you want to import the flow
2. Click the "Import Flow" button or use the menu
3. Select the JSON file containing the flow
4. Review the import preview showing flow details
5. Click "Import" to add the flow to your workspace

Import Multiple Flows

To import multiple flows at once:

1. Open the target workspace
2. Click "Import Flows"
3. Select multiple JSON files (using Ctrl or Cmd + click)
4. Review the list of flows to be imported
5. Click "Import All"

Exporting Workspaces

Export an entire workspace including all its flows and workspace-level variables:

1. Right-click on the workspace in the workspaces list
2. Select "Export Workspace"
3. Choose a location and filename
4. Click Save

{
  "name": "E-Commerce Testing",
  "description": "Automated tests for online store",
  "variables": [
    {
      "name": "baseUrl",
      "value": "https://shop.example.com",
      "scope": "workspace"
    }
  ],
  "flows": [
    {
      "name": "Login Flow",
      "actions": [...],
      "variables": [...]
    },
    {
      "name": "Add to Cart Flow",
      "actions": [...],
      "variables": [...]
    }
  ],
  "createdAt": "2025-12-01T10:00:00.000Z",
  "updatedAt": "2025-12-05T15:30:00.000Z"
}

Importing Workspaces

Import a complete workspace with all its flows:

1. From the main screen, click "Import Workspace"
2. Select the workspace JSON file
3. Review the workspace name and number of flows
4. Click "Import"
5. The workspace will be added to your workspaces list

Handling Import Conflicts

Name Conflicts

When importing flows or workspaces with duplicate names:

• Automatic Renaming: Record Flow automatically appends "(1)", "(2)", etc. to duplicate names
• Manual Rename: You can rename the imported item after import
• No Overwrite: Existing flows are never overwritten automatically

Variable Conflicts

When importing flows with variables:

• Flow Variables: Imported as-is with the flow
• Workspace Variables: Merged with existing workspace variables
• Global Variables: Not affected by imports (set separately)
• Duplicate Names: If a workspace variable with the same name exists, the imported value is ignored

Missing Dependencies

If an imported flow references variables that don't exist:

• The flow will still be imported successfully
• You'll need to create the missing variables manually
• Check the variable references in the imported flow's actions

Best Practices

Sharing Workflows with Teams

Preparing Flows for Sharing

Before sharing a flow with your team:

1. Review Variables: Ensure no sensitive data is hardcoded
2. Add Documentation: Include clear descriptions and comments
3. Test Thoroughly: Verify the flow works in a clean environment
4. List Prerequisites: Document any required setup (URLs, credentials format)
5. Export: Create the JSON export file

Distribution Methods

# Example Git workflow
git clone https://github.com/yourteam/flows.git
cd flows
# Add exported flow
cp ~/Downloads/login-flow.json ./e-commerce/
git add .
git commit -m "Add login flow for e-commerce site"
git push

Advanced: Manual JSON Editing

For advanced users, you can manually edit exported JSON files to:

• Batch update selectors across multiple actions
• Find and replace URLs or text patterns
• Programmatically generate flows
• Merge multiple flows

Example: Bulk Selector Update

If a website changes its selectors, you can use find/replace in a text editor:

# Before: Old class name
"selector": ".old-button"

# After: New class name
"selector": ".new-button"

# Use find/replace in your editor to update all instances

Validation

After manual edits, validate your JSON:

• Use an online JSON validator (jsonlint.com)
• Test import in Record Flow with a copy first
• Run the imported flow to verify functionality

Troubleshooting

Common Use Cases

Related Topics