62 Power Automate Desktop ideas that are actually worth automating

Opening Power Automate for desktop is the easy bit. Choosing a job that will survive contact with the real world is harder.

A good desktop flow takes a stable, rules-based task off somebody's screen. A bad one automates a messy process, breaks when a button moves and quietly enters the wrong data into the wrong system.

This guide gives you 62 practical ideas, but it also helps you choose the right first one, check the licensing and build something another person can support.

What Power Automate for desktop is good at

Power Automate for desktop—often shortened to PAD—is Microsoft's robotic process automation (RPA) tool for Windows. It can work with files, folders, Excel, PDFs, browsers, terminal emulators and Windows applications. It can also use connectors, web services, databases and scripts where the design calls for them.

The best use case is normally a job that:

• follows written rules;
• starts with a predictable input;
• repeats often enough to repay the build;
• has a clear success result;
• can be retried without creating duplicates; and
• has an owner when the application or process changes.

Do not reach for screen clicks first. Microsoft's desktop-flow performance guidance recommends this order:

1. a cloud connector;
2. an application-specific or file-specific action, such as Excel, PDF or file actions;
3. browser or UI automation; then
4. image recognition, mouse coordinates, keystrokes or the clipboard.

That order matters. An Excel action that addresses a worksheet directly is normally easier to support than a recording that clicks cells by position.

Check the licence before you build

“Power Automate Desktop is free” is only a partial answer.

Microsoft does provide local desktop-flow capabilities at no extra cost for some Windows and account combinations. The organizational features people often expect—cloud triggering, scheduling, sharing, attended bots and unattended execution—have separate account, operating-system and licensing requirements.

What you need	Check before building
A personal flow you start locally	A Microsoft account can use Power Automate for desktop at no extra cost, with important limits around organizational collaboration and cloud orchestration.
A flow shared and managed by a team	Microsoft positions Power Automate Premium for creating, managing, sharing and running organizational desktop automation in attended mode.
A desktop flow started by a cloud flow	Confirm the account, environment, machine registration, Windows edition and Premium entitlements. Windows Home can author and run locally, but Microsoft says it cannot use cloud runtime.
A flow that runs with nobody signed in	Unattended RPA needs Process capacity allocated to the machine, plus the appropriate Premium entitlement for the people building and managing it.
A Microsoft-hosted automation machine	Check the Hosted Process licence and its Windows, Intune and Microsoft Entra prerequisites.

Microsoft changes packaging over time. Use the current Power Automate licence types and desktop-flow prerequisites for the tenant you are buying for. Do not approve a production design from an old blog's “no licence needed” sentence.

62 Power Automate Desktop ideas

Treat these as problem prompts, not promises that every system can be automated safely. Confirm the application's rules, the data sensitivity and the available integration before building.

Files, folders and documents

1. Tidy a download folder. Move files into dated or client folders using filename, extension and modified-date rules.
2. Rename a document batch. Read a naming map from CSV or Excel, validate every match, then rename the files consistently.
3. Route an intake folder. Send valid files to Ready, incomplete ones to Needs review, and duplicates to a quarantine folder.
4. Check a delivery pack. Confirm that every expected filename is present before a case, project or month-end pack moves forward.
5. Create a folder manifest. Record filename, path, size and modified date in a CSV for review or audit evidence.
6. Compare two folder inventories. Identify missing, added or changed files before a migration or handover.
7. Archive old working files. Move files older than an agreed date into a controlled archive after an explicit dry-run report.
8. Build a ZIP handover pack. Collect approved files, compress them and produce a manifest so the recipient can check completeness.
9. Convert approved Word files to PDF. Open named documents, save PDF copies and keep the originals unchanged.
10. Split or combine PDFs. Create one pack per case, or extract specified pages, using a checked index rather than visual guesswork.

Power Automate's file actions cover common file, CSV and folder operations. Add a preview mode before any bulk move, rename or delete.

Excel and tabular data

11. Combine monthly CSV exports. Read every approved file, add source and import-time columns, then produce one controlled workbook.
12. Clean a spreadsheet export. Trim spaces, standardize dates, replace known codes and flag rows that cannot be converted safely.
13. Compare two system extracts. Join on a stable key and create Matched, Missing and Different exception sheets.
14. Populate a standard report template. Write validated data into a locked-down workbook without rebuilding the layout each time.
15. Create an exception workbook. Filter a large extract to the records that actually need a human decision.
16. Format a recurring report. Apply widths, number formats, sheet names and a run timestamp consistently.
17. Run an existing Excel macro. Let PAD prepare the input and call a reviewed macro, while keeping ownership of the VBA clear.
18. Reconcile transactions. Compare bank, payment, order or ledger exports and surface unmatched records without auto-posting them.
19. Create one file per team or customer. Filter a master table, write separate outputs and verify the row count in every file.
20. Archive a timestamped workbook. Save a read-only evidence copy before replacing the operational version.

Microsoft's Excel actions can launch or attach to Excel, read and write cells or data tables, manage worksheets and run macros. Use data-table operations instead of clicking thousands of cells.

Browsers and internal web applications

21. Download a daily portal export. Sign in through an approved method, choose the correct period, download the file and verify its name and size.
22. Upload validated records to a portal. Read only approved rows, submit them one at a time and store the portal's confirmation reference.
23. Extract a table from an internal webpage. Capture the table into a data structure, then write it to Excel with the source URL and run time.
24. Work through paginated results. Stop on a clear end condition and protect against repeatedly processing page one.
25. Check published values. Compare permitted public or partner data with an approved baseline and report changes.
26. Capture evidence after an update. Save a confirmation number and a screenshot that excludes secrets or unrelated personal data.
27. Complete repetitive internal forms. Populate fields from a reviewed input table, leaving judgement calls for the operator.
28. Verify a submitted record. Reopen it, read back the key fields and compare them with the source before marking the row complete.
29. Move records between old and new web interfaces. Use a migration queue, stable IDs, checkpoints and a reject path—not one long recording.

Browser automation is not permission to harvest any website. Respect access controls, contractual terms, robots policies, rate limits, copyright, privacy and the site's intended use. Never build a flow to bypass a CAPTCHA or other security control.

Desktop and legacy applications

30. Enter approved data into a legacy ERP screen. Validate the record first and capture the ERP reference after saving.
31. Copy data between two desktop applications. Use named variables and field checks instead of leaving data on the clipboard.
32. Populate a line-of-business application. Navigate with UI elements, not fixed screen coordinates, wherever the application exposes them.
33. Read a terminal-emulator screen. Extract values from a stable terminal session and send exceptions to an operator.
34. Create documents from a desktop case system. Open each approved case, generate the document and confirm the expected output exists.
35. Transfer reviewed records into accounting software. Keep posting or payment approval outside the bot unless controls explicitly permit it.
36. Compare values across two application windows. Flag differences instead of automatically choosing which system is right.
37. Run a reviewed script for a difficult transformation. Use PowerShell, Python or another supported scripting action when a transparent script is safer than hundreds of designer actions.
38. Wrap a command-line utility in a controlled flow. Validate arguments, capture the exit code and keep the command output with the run log.

UI automation is sensitive to changed window titles, layouts, permissions and selectors. Microsoft's UI automation troubleshooting recommends testing and repairing selectors when an element or window can no longer be found.

Email and communications

39. Save attachments from an approved mailbox. Retrieve only messages matching a narrow sender, subject and attachment rule.
40. Route attachments by reference number. Extract the identifier, verify it against a case list and quarantine anything ambiguous.
41. Turn a structured email into a work item. Parse known fields, validate mandatory values and create a draft record for review.
42. Prepare templated draft emails. Fill a reviewed template with case data but leave sensitive or consequential messages for a person to send.
43. Distribute a completed report. Confirm the file exists, the reporting period is correct and the recipient list comes from an approved source.
44. Build a mailbox exception log. Record messages that failed parsing without copying the full body into an insecure spreadsheet.
45. Hand a desktop result to Microsoft 365. Use an available Outlook, SharePoint, Teams or OneDrive connector action to publish the result or notify an owner.

Desktop flows do not magically gain the same triggers and entitlements as cloud flows. Microsoft now exposes selected cloud connector actions in desktop flows, but connections, environments and licences still matter.

Finance, operations and casework

46. Prepare an invoice for review. Extract text or tables from a digital PDF, validate supplier and totals, then create a review record.
47. Match invoice, purchase order and receipt exports. Surface mismatches; do not approve payment because three strings happen to match.
48. Assemble an expense evidence pack. Rename receipts, create a manifest and flag missing dates, amounts or claim references.
49. Prepare a bank reconciliation exception list. Match only on agreed rules and keep ambiguous transactions for finance review.
50. Enter shipping or consignment details. Copy approved data into a carrier or warehouse application and save its confirmation number.
51. Produce a daily sales pack. Combine source exports, update the standard workbook and log the source periods used.
52. Create a stock exception report. Compare system stock with a count file and highlight differences over an agreed tolerance.
53. Assemble a quality or inspection pack. Collect forms, photos and readings into a named folder structure and report missing evidence.

Scanned documents are less predictable than digital PDFs. OCR can misread dates, decimal points and identifiers. Route low-confidence or high-impact fields to a person, and consider a document-processing service when layout variation is the real problem.

IT and data operations

54. Collect a workstation inventory. Record approved machine, operating-system, disk and application details without collecting employee content.
55. Run a repeatable health check. Test agreed services, folders, endpoints or log files and write one timestamped result.
56. Restart an approved Windows service. Do it only within a change procedure, after checking dependencies and recording the outcome.
57. Gather logs for a support case. Copy the required files, remove unnecessary sensitive data and build a manifest.
58. Run a read-only database query and export the result. Use a least-privilege account and parameterized, reviewed SQL.
59. Transfer a controlled file through FTP or SFTP. Verify the destination, size and checksum or acknowledgement before archiving the source.

Administrative actions can cause more damage than ordinary data entry. Use least privilege, separate development from production and require approval for identity, service, security or destructive changes.

Small personal and team automations

60. Normalize copied text. Remove unwanted line breaks, standardize separators and place the cleaned result in a new file or variable.
61. Run a repeatable application smoke test. Open the app, exercise a small approved path and report the exact step that failed.
62. Build an end-of-day handover pack. Gather the day's approved outputs, create a manifest and leave a clear list of exceptions for tomorrow.

Pick your first idea with this six-question test

Score each candidate from 0 to 2 on these questions:

1. Rules: Could another person follow the process from written instructions?
2. Repetition: Does it happen often enough to justify maintenance?
3. Input quality: Are the files, fields and identifiers predictable?
4. Failure visibility: Will somebody know quickly if the result is wrong or missing?
5. Safe recovery: Can you retry without duplicating records, emails or payments?
6. Ownership: Is there a named person responsible when the process or application changes?

Start with a high-scoring, low-impact task. “Rename and route 40 files every morning” is a better first build than “operate our finance system overnight.”

A reliable desktop-flow pattern

Most production-worthy flows need more than recorded clicks. Use this shape:

1. Load configuration. Read paths, URLs, tolerances and non-secret settings from one controlled place.
2. Validate the environment. Confirm the expected application, folder, workbook, account and input are available.
3. Create a work queue. Give each item a stable ID and a status such as Pending, Processing, Complete or Needs review.
4. Process one item. Keep the repeatable unit small enough to retry safely.
5. Read back the result. Check the saved reference, value, file or confirmation instead of assuming a click worked.
6. Handle the error. Record the item, action, time and useful error detail; then continue or stop according to the risk.
7. Close applications and files. Release Excel, browser and application sessions cleanly.
8. Report the run. Show completed, skipped and failed counts, plus the location of the exception list.

Microsoft documents action-level error handling, On block error, Get last error, Stop flow and logging in its desktop-flow performance guidance. It also recommends specific Wait for actions and timeouts instead of scattering generic delays through the flow.

Ten rules that keep desktop flows supportable

1. Prefer connectors, APIs and application actions over visual automation.
2. Prefer UI-element selectors over coordinates, images and keystrokes.
3. Keep credentials out of plain-text variables, files and screenshots.
4. Validate before writing, sending, deleting or posting.
5. Make each work item safe to retry.
6. Use subflows with clear inputs and outputs for repeated logic.
7. Add explicit error and timeout paths before production.
8. Log decisions and identifiers, but minimize personal or secret data.
9. Test with the real screen resolution, permissions, regional settings and application version used at runtime.
10. Give every production flow an owner, a support note and a retirement plan.

What not to automate with desktop RPA

Avoid or redesign a candidate when it requires:

• bypassing a CAPTCHA, multifactor prompt or other security control;
• scraping or reusing data without permission;
• autonomous hiring, disciplinary, medical, legal or credit decisions;
• payments, account changes or destructive actions without proportionate approval;
• interpreting highly variable documents with no confidence threshold;
• continuous employee surveillance;
• a personal password embedded in the flow; or
• an unstable interface with no budget or owner for maintenance.

Sometimes the right answer is a connector, an API, a better source system or removing the task entirely.

Official Microsoft references

• Introduction to desktop flows
• Power Automate for desktop prerequisites and limitations
• Power Automate licence types
• Power Automate for desktop actions reference
• Desktop-flow coding guidelines
• Run unattended desktop flows

Building desktop flows that other people must rely on? Join the Power Automate Builders Space for practical patterns, current Microsoft changes and peer discussion.