Importing a flow lets you upload a flow definition file (JSON) into your RapidPro.app workspace. This is useful for moving flows between workspaces, restoring a saved version, or sharing templates across teams.
Warning: If an imported flow has the same name as an existing flow in your workspace, the existing flow may be replaced and its history can be lost. Always verify names before importing.
Import a flow safely (without replacing the wrong one)
If you already have a JSON file and just need the fast path, follow this:
- Decide where to import from (Flows or Workspace settings)
- Open the ☰ menu and click Import
- Upload your .json file and confirm
- Find the imported flow and review + test in the simulator
You’re done. The flow is now available in your workspace and ready for review and testing.
Step-by-Step Process
You can start the import process from either location:
- The Flows section in your workspace (recommended), or
- The Workspace settings page
- Log in to your RapidPro.app workspace.
- Navigate to Flows (recommended) or Workspace settings.
[CAPTURE: Workspace navigation showing both “Flows” and the Settings (gear) entry point.]
- Look for the ☰ menu (top-right).
- Click the ☰ icon to open the dropdown menu.
- Click Import.
[CAPTURE: Top-right ☰ menu open with “Import” highlighted.]
- In the import window, click Choose file (or the upload area).
- Select the flow file you want to import (typically a .json file).
- Click Import to confirm.
[CAPTURE: Import dialog showing a selected file name and an “Import” button.]
- Return to the Flows list.
- Find the imported flow by name.
- Open it in the flow editor and review:
- Connections between nodes
- Keywords/triggers (if included)
- Expiration settings (if applicable)
- Run a full test using the simulator and check the action log.
[CAPTURE: Flows list showing the imported flow, then the flow editor open for a quick review.]
Common Issues & Quick Fixes
Problem: Import replaced an existing flow.
Fix: Check if the imported flow had the same name as an existing flow. Re-import using a renamed version (rename in the source workspace before exporting, or rename immediately after import if your UI allows). Use a naming convention like Program – Flow Name – v2 or Template – Flow Name.
Problem: I can’t see the Import option.
Fix: Confirm you’re in the right area (Flows or Workspace settings). Check your role—import typically requires Editor or Admin. Look for a grouped option like Export & Import if your UI combines them.
Problem: The flow imports, but doesn’t behave as expected.
Fix: Review dependencies in the destination workspace: contact fields referenced in Update Contact, groups referenced in Add/Remove Group, and integration settings like webhook URLs. Then run a full simulator test and check the action log step-by-step.