Create desktop flows with Copilot
Power Automate for Desktop (PAD) is the application used to build, run, and manage desktop flows on a Windows PC. Copilot in Power Automate for Desktop brings natural language capabilities to desktop automation—helping you build desktop flows from descriptions and refine them through conversation.
Copilot capabilities in Power Automate for Desktop
Copilot in Power Automate for Desktop is accessible through the Copilot Chat panel in the PAD application. It can:
- Generate desktop flow actions from a natural language description, with recording placeholders for browser or UI tasks that you need to complete.
- Add actions to existing flows based on conversational prompts.
- Answer product questions about desktop flows—for example, explaining what a specific action does or how to accomplish a task in PAD.
- Summarize actions and subflows to help you understand what your desktop flows do.
Note
Copilot requires a work or school account. Creating flows and adding actions through natural language are preview capabilities. Flow creation currently requires an environment located in the United States. Product questions and action or subflow summaries are available in additional regions. Check the Copilot documentation for current availability and supported actions. Preview features aren't intended for production use.
Creating a desktop flow with Copilot
To create a desktop flow using Copilot, open the Power Automate for Desktop console. Enter your prompt in the Copilot area on the Home page. Alternatively, select the Copilot button in the upper-right corner of the console and select flow creation mode in the side panel.
Describe the automation process you want to build. For example, a Contoso employee responsible for daily pricing updates might describe:
"Open Excel and read the pricing data from the sheet named Price Updates. For each row, open the pricing portal website, log in, navigate to the product by entering the product code, update the price field with the value from Excel, and save the change. After processing all rows, close Excel and the browser."
After you submit the prompt, Copilot generates a flow and opens it in the designer for review. The pricing example includes browser and UI tasks, such as signing in and updating fields. Copilot inserts recording placeholders for those tasks rather than generating a complete working browser automation.
Complete each placeholder with the standard recorder or manually authored UI actions. Review all generated actions and provide any missing required parameters, such as the Excel file path. Then test the flow before you use it.
Complete browser and UI steps with the standard recorder
The standard recorder captures mouse and keyboard interactions with desktop and web application UI elements. Use it to complete the browser and UI steps that Copilot leaves as recording placeholders.
To complete those steps:
- Start the recorder from a recording placeholder. To record steps independently, select Recorder in the flow designer toolbar.
- Select Record and perform the required actions in the application or web page.
- Select Done to convert the recorded steps into desktop flow actions. When you start from a placeholder, the recorded actions replace it.
- Review the recorded actions, edit them as needed, and test the flow.
For example, record how you locate a product in the pricing portal and update its price. Review the recorded actions and configure them to use the product code and price from the current Excel row instead of fixed values. See Record desktop flows for more information.
Note
The standard recorder is separate from Record with Copilot (AI Recorder), which is deprecated and isn't available in Power Automate for Desktop.
Modifying desktop flows with Copilot
After you create a desktop flow with Copilot, the standard recorder, or manual action authoring, Copilot can help extend it by adding actions. Open the flow in the PAD designer, open the Copilot panel, and select Add a step that or the corresponding skill from the drop-down menu. Describe the actions to add:
- "Add a variable to track the count of rows processed and display the total in a message box at the end."
- "Add a message box that displays Pricing update complete."
Copilot adds supported actions at the end of the flow or beneath a selected action. Review the generated actions and complete any missing parameters or recording placeholders before you test the flow. Use the designer to remove or reorganize actions manually.
Tip
Before deploying an unattended desktop flow to run on a schedule, always test it in attended mode first—running it while watching the screen to verify that each action executes correctly. Unattended flows run in the background and are harder to diagnose if something goes wrong.