Export and import flows
You can export and import single flows, or a folder containing multiple flows. The export and import features enable you to share flows and tables between multiple Okta organizations, or share them with other people outside your organization.
To export a single flow, click the Export icon on the flow. If your folder displays your flows in a list view, click the gear icon on the flow, and then select Export. When you click Download, the flow is exported and saved as a .flow file to your local system.
You can also use a function card to export one or more flows as JSON objects. See Export Flow.
To import a single flow into your organization, complete the following steps:
- In the Workflows Console, select the folder where you want to place the imported flow.
- From the folder's dropdown Actions menu, click Import.
- Drag and drop your file into the dialog, or click Choose file from computer to browse your local filesystem. The file import begins immediately.
To export an entire folder, including all nested subfolders, complete the following steps:
In the Workflows Console, select the folder you want to export.
From the folder's dropdown Actions menu, click Export.
In the Export folder dialog, you can choose to export the current folder tree including content from all nested subfolders, or export only the current folder contents.
Click Download to save the exported .folder file to your local filesystem. This file contains all exported flows, tables, and subfolders.
The export function removes all connection account information and table data. After importing this file, you must create or assign application connections to use the flows. However, if you import the same flows or tables into the original Okta org, you can reapply your existing connections to the cards in those flows.
The export function maintains links between objects referenced by the flows. For example, if a flow calls a helper flow to process a list, the link between the parent and helper flows is kept.
If you export a folder containing referenced objects that aren't part of the folder, the export dialog warns that there are flows with missing references. When you import this folder, Okta requires you to recreate the referenced objects for the flows.
You can also use a function card to export a folder containing one or more flows as a single JSON object. See Export Folder.
The imported flows appear as new flows. They don't preserve any application connections, so you need to reconnect all applications.
For tables, the export action doesn't include any of the original table data. The import action recreates all tables according to the table schema listed in the export file, but the tables are initially empty. The limit of 100 tables in a folder remains.
If any of the imported flows refer to a flow not included in the export (for example, a helper flow called to handle a list), you need to specify a replacement flow to complete the import.
To import an Okta Workflows.folder file, complete the following steps:
In the Workflows Console, select the folder where you want to place the imported flows.
In the Actions dropdown menu, click Import.
Drag and drop your file into the dialog, or click the link to browse your local file system for the file.
Okta imports the content to the current folder, unless the import action would exceed the maximum folder depth of five levels. In this scenario, Okta provides the option to import the contents as a top-level folder instead.
When importing, Okta preserves the exported locations of any subfolders, along with their flows and tables.