8e48f41f-e82f-40f7-a433-7428a495dd39.jpg

Intelligent Automation Developer

20ee1a5e-eeac-45cd-91e2-11768d01c2d9.jpg

Currently, PAD does not allow to export/create backups of flows developed in Power Automate Desktop.

This automation uses a simple workaround of copying each Flow's data as plain text and storing it in a .subflow file for subflows and .arg file for arguments, at a user-defined backup location.

1. The automation prompts the user to choose a backup location on disk in a Browse Folder dialog.
2. The automation extracts a list of flows in PAD "My flows" page and offers a choice to enter Flow names to extract or extract All flows.
3. The automation creates a top-level folder with the name of the Flow in the format "exported_FlowName".
4. The automation opens selected Flow Designer Panel and loops through each Argument, storing Argument properties in .arg file in Arguments/Input or Output folder.
5. The automation loops through each Subflow (including Main), creates a .subflow file and writes the data in WinAutomation syntax.

Need to export a PAD Flow? Use this to create a backup of a Flow from PAD by extraction Arguments and Subflow data into a text file.

35e3c653-0c67-4516-8ad7-aa33acabb695.jpg

Currently, PAD does not allow to import flows developed in Power Automate Desktop. This automation is designed to leverage PAD_ExportFlows ability to extract each Flow data, including arguments data into .arg files and subflow (including Main) data into .subflow file.

This automation uses a simple workaround of pasting each Subflow data that was previously exported into a .subflow and .arg file at a user-defined backup location on disk.

1. The automation prompts the user to choose a previous backup location on disk in a Browse Folder dialog. 
2. If the user chooses top-level folder that contains several flow-named folders, the automation will import all subfolders as new flows with the corresponding name. 
3. If the user chooses a specific flow-named folder, only that flow will be imported.
4. The automation checks PAD "My flows" page to identify if the flow already exists. In this case, it will not import the current flow to avoid conflict and overwriting of an existing flow.
5. The automation creates a new flow with the name defined by the backup folder.
6. The automation loops through each chosen Flow by opening it in PAD Designer panel, loops through each Subflow (including Main), imports data (including flow Arguments) from backup .arg and .subflow file that contains all of the data in WinAutomation syntax in the previously named folder.

Need to import a PAD Flow that was exported with PAD_ExportFlows? Use this to import a flow into Power Automate Desktop.

About me