Power Automate Desktop

What is Power Automate Desktop?

Power Automate Desktop is the Windows app for building and running desktop flows, the robotic process automation side of Power Automate. A desktop flow clicks buttons, types into fields, reads values off the screen, moves files, and drives one application after another, the same way a person would with a mouse and keyboard.

Microsoft now calls the app Power Automate for desktop, and it comes preinstalled on Windows 11. It ships with more than 400 prebuilt actions for files, folders, Excel, email, browsers, databases, and Windows applications.

The tool earns its place when an application has no usable API. Instead of talking to the service underneath, the flow operates the interface a human already uses. That makes it a fit for older line-of-business software, supplier portals that only offer a browser, and any screen you cannot reach another way.

How you build a desktop flow

You build a flow in the designer by dragging actions into order and filling in their inputs. Most actions produce output that a later step can read from a variable, so values move from one step to the next.

The recorder gives you a head start. You perform the task once, and Power Automate Desktop turns your clicks and keystrokes into actions. A recorded flow is rarely ready for production, though. Wait steps, error handling, and reliable selection of on-screen elements still need work before the flow can run on its own.

UI elements are how a flow finds a button or a field. Rather than relying on fixed screen coordinates, the flow matches an element by its properties, which survives small layout changes better. A redesign of the target application can still break the selector, so these need maintenance.

Subflows split a long automation into smaller named blocks. A main flow might sign in, call a subflow for each record, then write a summary file at the end.

Attended and unattended runs

An attended run happens on a person's machine, with someone there to start it or hand it work. This suits tasks where the employee picks a case, judges an exception, or decides between steps.

An unattended run happens on a managed machine with nobody signed in. A cloud flow or a schedule starts it. Unattended running needs the right licence, a configured machine, stored credentials, and monitoring, because no one is watching when something goes wrong.

A desktop flow drives real application sessions, so a locked screen, an unexpected pop-up, a resolution change, or a Windows update can all affect a run. Managing the machine the flow runs on is part of the solution, not an afterthought.

Power Automate Desktop versus API automation

An API is a stable technical contract built for software. Its fields and error codes are meant for other programs, so an integration built on an API tends to survive visual changes and can run without an interactive Windows session.

UI automation works against nearly the same interface a person sees. That is what lets it automate legacy software, but the flow inherits the speed and fragility of that interface. A renamed label or an extra dialog can stop a run.

Reach for an API or a connector first when one covers the step you need. Use Power Automate Desktop for the part that is only reachable through a screen. A hybrid process often uses a cloud flow to orchestrate and a desktop flow only for the missing piece.

Common use cases

• Moving data out of legacy software. Open an old accounting package, read the open items off the screen, and drop them into an Excel file that a cloud flow then sends to SharePoint.

• Processing files from a portal. Sign in to a supplier portal that only has a browser, download the available files, check their names, and file them in the right folder.

• Bulk data entry. Take rows from a spreadsheet and key them into a system that has no import feature of its own.

• Reconciliation across systems. Pull figures from two applications that do not talk to each other and flag the differences.

All of these are sensitive to interface changes. If the underlying system offers a stable API, that route is usually worth the switch.

What to watch out for with Power Automate Desktop

Interface changes break flows. A moved button or a new pop-up can stop a run mid-task. Plan for time-outs and error paths, and capture the step, the input, and a screenshot when something fails.

Half-finished runs are dangerous. Make sure a flow that stops partway does not process the same transaction twice when it runs again.

Credentials need care. Do not store passwords as plain text in variables or scripts. Use the supported connection and credential options, and limit who can edit or start a flow.

Someone has to own it. Test after updates to Windows, browsers, and the target applications, track run times and failure rates, and give each flow an owner. A desktop flow nobody looks after tends to fail quietly until a colleague notices the work has stopped.