Use Softomotive's WinAutomation with desktop flows


  • WinAutomation and ProcessRobot are no longer supported. Migrate your flows to Power Automate for desktop.
  • Windows recorder (V1) is deprecated and no longer works. Migrate your flows created to Power Automate for desktop or delete them.

You may migrate your flows to Power Automate. See the Power Automate Desktop documentation to learn about the evolution of WinAutomation.

Here are some tips before you start using WinAutomation with desktop flows.

  1. Your Power Automate Attended RPA license (paid or trial) gives you full access to WinAutomation. This document will guide you through getting WinAutomation Processes running with Power Automate.

  2. Automation scripts in WinAutomation are called Processes. In Power Automate, automation scripts are called cloud or desktop flows*.

  3. Before you create a WinAutomation Process, check the list of connectors to see if the application you want to automate already has a connector. If it does, consider creating a cloud flow instead of a desktop flow. You might also build your own connector. In general, API-based connectors provide a better experience than UI automation in terms of scalability, reliability, and lower cost.


To run WinAutomation as part of Power Automate, you will need to:

  1. Ensure your machine meets the requirements for desktop flows.

  2. Install the desktop flows app, and then install and configure the on-premises data gateway.


You must have the latest version of WinAutomation and Power Automate to record, test, or run UI automation.


You need to have a Power Automate Per user plan with attended RPA to use Power Automate and WinAutomation. If you don't have a paid plan, you can start a trial by going to Power Automate.


Install WinAutomation

  1. Download the WinAutomation installer.

  2. Run the WinAutomationSetup.exe file. This file is likely in your Downloads folder.

  3. Follow the instructions in the WinAutomation installer to complete the installation. During installation, ensure the License Type is set to Microsoft Power Automate.

Sign in to WinAutomation

  1. After the installation completes, start the WinAutomation Console from the Windows start menu.

  2. The application will start and prompt you to login. Enter the user credentials you use for Power Automate. If you don’t have a valid license, you will see this error message. You can also visit the pricing page to learn more about this license or to get a trial license.

    Screenshot of a License error.


    You will need your tenant administrator to grant consent to use your Power Automate Work or School account with WinAutomation. For that, your admin needs to install WinAutomation, sign in with their tenant administrator account, and then grant consent.

    Screenshot of the dialog that requests for permissions.

  3. When you are asked to create a Master key during sign in, create one.

  4. Once signed in, you will see the WinAutomation console with a few example Processes. To get started, go to Options > Help > Getting Started, and then go through a few examples of creating simple Processes or check out information from WinAutomation docs: Building a Simple Process. You can learn more from WinAutomation getting started tutorials.

You can now create your own WinAutomation Processes and test them locally.

Run WinAutomation Processes from Power Automate

  1. Once you have created your automation Process in WinAutomation, you can run it from a cloud flow in Power Automate in attended or unattended mode.


    Learn more about creating and running desktop flows.

  2. Create a new desktop flow. Delete the default first step of “Record app”.

    Screenshot of the option to delete the record app step.

  3. Select New step, select WinAutomation, and then select the Run WinAutomation action.

    Screenshot of the Run WinAutomation action.

  4. In the Run WinAutomation card, fill in the Process Path and any optional command line arguments for the WinAutomation Process that you want to run.

    Screenshot of the Run WinAutomation card.


You must create and store WinAutomation Processes locally. Process Path is a case-sensitive path in the WinAutomation Console for the Process, from a base directory of My Processes in the Folders Pane on the left side. If you have put the Process in a subfolder, you will need to include that information in the ProcessPath. Don’t put quotes around the Process Path.


You can use desktop flows inputs and Dynamic content in the target WinAutomation Process path and arguments from Power Automate flow.

  1. You can now save and test your Windows recorder (V1) flow to see how it launches the WinAutomation Process.

  2. You can then add the Windows recorder (V1) flow into a cloud flow. You can even connect to other Power Automate connectors and triggers.

  3. You can then select attended or unattended as the run type.


    In your WinAutomation Process, you can use the Get Command Line Arguments action to retrieve the command line arguments. The arguments are in an array. Use their index to reference each argument.


    Do not pass sensitive text such as passwords through the command line arguments.


    If you’re running desktop flows on an unattended cluster, ensure that WinAutomation is installed on all machines on which the target Process is copied. For more information on attended and unattended desktop flows, click here.

  4. You can save and then run the flow and see it launch the WinAutomation Process. The Windows recorder (V1) flow will return after the WinAutomation Process run completes. You can view the run results from Power Automate. If the Process fails, you can see the error messages as well.


    If you get exceptions, you may not have the latest Power Automate installed. Install the latest Power Automate.

  5. If you want WinAutomation to capture a screenshot when a Process fails, do the following:

  6. From the WinAutomation Console, right click on a Process, select "Edit Process's Properties". Go to the "Error Handling" tab and choose "Override Default Options". Click "Add screenshot to logs" and save. Now if a Process fails, you can view the screenshot captured at runtime from the Windows recorder (V1) flow run details. For more information on Process properties, see WinAutomation docs: Process Properties.

    Screenshot of the process properties dialog.

Currently you have to use certain WinAutomation steps to write results and outputs from the process into a file in the cloud share or email the results out. Then you can use connectors from Power Automate to access and use those results.

How to obtain an RPA trial license

Log in to Power Automate then select the Desktop flows tab under My flows. You'll see the trial dialog from which you can start the trial.

Screenshot of the start a trial or buy a license options.

If you already have a paid plan or you used a trial previously, you cannot start a new trial. In this case, you will need to ask your administrator to buy or start a trial of the Power Automate Per user plan with attended RPA. They can make the purchase by going to Billing > Purchase services in the Microsoft 365 admin center, and then searching for the right plan.

Screenshot of the per user plan with attended RPA.

Finally, once they have purchased a plan or gotten the free trial, they need to assign that plan to a user.


When you assign a plan to a user, it may take few minutes before the assignment becomes effective.


Troubleshooting WinAutomation licensing issues

If you are receiving licensing errors during the launch of WinAutomation, ensure the user you’re logging in as has a valid Power Automate RPA license. To confirm this:

  1. Go to Power Automate and sign in.

  2. Select My flows on the left navigation bar.

  3. Select desktop flows on the page on the right. You should see you can create new desktop flows there if you have the correct license.

  4. You may need to start a trial or ask your administrator to do it.


    The license is cached when users launch WinAutomation while connected to the Internet.

To reset the license information stored by WinAutomation, you can delete the following file: %localappdata%\Softomotive\WinAutomation\msalcache.bin3.

Troubleshooting other issues

Follow the links in this section to troubleshooting issues you may experience.



Best practices for creating processes

Here are some tips for you to consider when you create processes.



Learn more