Import and Export

Membrane provides several ways to transfer workspace elements (integrations, actions, flows, field mappings, data sources, data links, and custom connectors) between workspaces. This is commonly used to move configurations from development to production.

What Gets Transferred

Transferred:

• Integration configurations (which connectors are used)
• Actions, flows, and field mappings
• Data sources and data links
• Custom connector source code
• Element structure and relationships

NOT transferred:

• Integration parameters (clientId and secrets, OAuth configurations)
• Workspace settings
• Internal API definitions
• Connection credentials

Console UI

The Console provides a visual interface for importing and exporting workspace elements:

1. Navigate to Settings > Import/Export in your workspace
2. To Export: Click the export button to download all workspace elements as a zip file
3. To Import: Upload the zip file to your target workspace using the import feature

This method is ideal for one-time transfers or manual migrations between workspaces.

API

For programmatic or automated transfers, use the Membrane API:

Export workspace elements:

curl -X GET "https://api.integration.app/workspaces/export" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  --output workspace-export.zip

See the Export Workspace API Reference for details.

Import workspace elements:

curl -X POST "https://api.integration.app/workspaces/import" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -F "[email protected]"

See the Import Workspace API Reference for details.

This method is ideal for CI/CD pipelines, automated deployments, or custom tooling.

CLI

Membrane CLI lets you pull and push workspace elements as YAML files, making it possible to version-control your integration configurations and use standard development workflows.

npm install -g @membranehq/cli

# Pull workspace elements to local files
membrane pull

# Push local changes to workspace
membrane push

See the Membrane CLI npm page for full documentation on installation, configuration, and usage.

This method is ideal for local development, version control, and diff tracking.

Comparison