Power Automate Desktop Flows: RPA for Systems With No API
When a system has no API, Power Automate desktop flows drive it the way a person would. A guide to when desktop-flow RPA is the right tool and how to keep it reliable.
Power Automate has two halves. Cloud flows connect systems through their APIs. Desktop flows drive the screen the way a person would, clicking and typing through an application that has no API at all. When a critical step lives in old or closed software, desktop flows are often the only way to automate it. They are also the part most likely to break if you build them carelessly. Here is how to use them well.
What desktop flows actually do
A desktop flow records and replays interactions with a Windows application: open this window, read this field, type into that box, click submit. It is robotic process automation in the literal sense, a software robot operating the user interface. This is what lets Power Automate reach legacy ERPs, terminal emulators, thick-client apps, and portals that were never built to be integrated.
When you genuinely need them
- A key system has no API and cannot be changed or replaced soon.
- The work lives in a legacy desktop or terminal application.
- A vendor portal only accepts manual entry, with no integration option.
- You need to bridge two systems quickly while a proper integration is planned.
When not to use them
If the system has an API or a Power Automate connector, use a cloud flow instead. Cloud flows are steadier, run in the background, and do not break when a screen layout changes. Reaching for a desktop flow when a connector exists adds fragility for no reason. We cover that choice in detail in RPA versus workflow automation.
Keeping desktop-flow RPA reliable
- Prefer stable UI selectors over screen coordinates, so a moved window does not break the bot.
- Build explicit error handling and retries for slow screens and unexpected popups.
- Decide attended versus unattended early, and make sure the machine and login are always available for unattended runs.
- Log every run so a failure tells you exactly which step and screen broke.
The rule we follow
Use a cloud flow wherever a connection exists. Use a desktop flow only for the steps that can be reached no other way, and wrap those steps in real error handling. That keeps the fragile part small and the rest of the pipeline solid.
Where to go next
Our Power Automate consulting service covers both cloud and desktop flows. For how an engagement runs, see our guide to Power Automate consulting, or book a strategy session.
Have a process worth automating?
Book a strategy session. We will find the real driver, tell you honestly what we would do about it, and show you the numbers.