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.Documentation Index
Fetch the complete documentation index at: https://docs.getmembrane.com/llms.txt
Use this file to discover all available pages before exploring further.
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
- 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:- Navigate to Settings > Import/Export in your workspace
- To Export: Click the export button to download all workspace elements as a zip file
- To Import: Upload the zip file to your target workspace using the import feature
API
For programmatic or automated transfers, use the Membrane API: Export workspace elements: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.Comparison
| Method | Best For | Pros | Cons |
|---|---|---|---|
| Console UI | One-time transfers, non-technical users | No setup required, visual interface | Manual process |
| API | Automation, CI/CD pipelines | Scriptable, integrates with existing tools | Requires API authentication setup |
| CLI | Local development, version control | Full local workspace sync, diff tracking, IDE integration | Requires CLI installation |