Power Automate Desktop RPA: Automate Software With No API

Your management software dates from 2011, runs on a server in a cupboard, and every morning someone retypes the orders that came in by email. The vendor has no API, or sells one at a price that makes no sense for you. Your carrier's website, meanwhile, wants every shipment copied into a web form. No connector for any of it.

Power Automate Desktop can replay those clicks so that nobody has to. That is what RPA is. Here is what it is worth, what it costs to maintain, and the test that tells you whether it is the right tool or papering over the cracks.

What RPA does with Power Automate Desktop

RPA stands for robotic process automation: a program drives the interface of another piece of software the way a person would. It opens the application, clicks a menu, types into a field, reads what is on screen, saves. The "robot" here is a script, nothing more.

Power Automate Desktop comes preinstalled on Windows 11 and is a free download on Windows 10, for local use. As soon as you want to trigger it from the cloud or run it with nobody at the screen, you need a licence: per user for attended mode, per machine for unattended mode, in the region of a few dozen to a few hundred euros a month depending on the case; prices move, so look up Microsoft's pricing page when you decide. Typical cases: an old line-of-business package, a supplier, bank or government website, a report to extract every morning.

Recording the clicks, then making the flow robust

The recorder captures your actions and generates the flow steps. It is a starting point, never a finished product. What it produces relies on selectors, the description of each button or field. Recorded as-is, they contain screen positions or indexes like "third button". The day the vendor adds a button, everything breaks.

The real work is cleaning those selectors to keep only stable identifiers, and handling the cases where things go wrong. A robust flow waits for an element to appear rather than a fixed number of seconds. It recognises an unexpected error window and knows how to close it. It verifies what it read before it writes. It logs every processed line so it never enters the same order twice, and picks up where it stopped after a crash.

On failure, it takes a screenshot and posts it to a Teams channel with the line number concerned. A person takes over that one case, not the whole day's work.

A dedicated machine, not somebody's laptop

In unattended mode, the flow runs on its own machine, often a virtual one: always on, session signed out, screen resolution fixed, software updates controlled by you, with a service account that has its own rights in the business application. The Power Automate machine runtime is installed there and registered to your environment. If volume grows, several machines go into a group.

Attended mode runs on the user's own computer, triggered by them. It is useful for assisted data entry during the day, not for an overnight batch. In both cases, the credentials for the business application are never in the script: they go into the flow's sensitive variables or a secrets vault.

Patch or cure: when to migrate instead of automating

RPA is a quick fix rather than a cure, and a good quick fix has its place. It goes live in a few weeks, leaves the software untouched, and gives time back immediately. But it is fragile by nature, it costs maintenance every time a screen changes, and it depends on a machine that has to stay on.

Good case: software that will stay for at least three years, a repetitive task with moderate volume, a team that can watch the alert channel. Bad case: the vendor offers a file import or an API (the file always wins), the software will be replaced within twelve months, or the process itself is broken. Automating a bad process speeds it up; it does not fix it. And if what you want to drive by clicking is a home-made spreadsheet, the answer is not RPA but a proper application, as we explain in Power Apps or Excel.

If you are in the good case, decide from day one who watches and who repairs: an RPA flow without maintenance stops at the first software update. The scope and the machine are settled during scoping, and the build is then delivered at a fixed price set during scoping.