Exporting and Importing Folders

Export Folder and Import Folder commands are available for:

• Sharing Flows and Tables with yourself if you belong to more than one organization
• Sharing Flows and Tables with users who are outside your organization

For sharing with other users inside your organization, see Sharing and Collaborating on Flows.

Exporting using the “Export” command

The “Export” command is located on the folders’s cog menu that appears when you hover over a folder, such as My Folder. You export all of the Flows and Tables in a folder at one time, so create a new folder if you want to export only a subset of an existing folder.

Choosing the command results in the creation of a file that is downloaded to your computer. The file name ends in “.flopack”. You can share that file with another user or use it yourself to import it into a new organization, following the instructions below.

Sharing through the Export command strips out all accounts and all data – you’re just sharing the logic of the Flows and the schema of Tables. The receiving user will have to assign new accounts in order to use the Flows.

Note: Links between Flows are maintained, e.g. if one Flow calls a child Flow to process a list. You are warned if any of the Flows link to another Flow that is not included in the folder because the Import will require that a new Flow be named in its place before the import can succeed. *There is a known bug where a child Flow that calls itself recursively cannot be exported. The workaround is to remove the recursive call, export, and then fix up on import.

Importing using the “Import” command

Once you have a “.flopack” file, mouse over to the folder (such as My Folder) where you want to place the imported Flows and choose the “Import” command off of the folder’s cog menu. Click the “Upload” button to choose a file or simply drag & drop a file into the dialog to start the upload.

The Flows you import show up as new Flows with no data and you need to re-connect to any applications using your accounts. Tables you import are empty (no rows).

If any of the imported Flows refer to a Flow that wasn’t included in the export (e.g. a child Flow called to handle the items of a list) you’ll have to specify a replacement Flow in order to complete the import.