Create and test Selenium IDE flows
This section covers topics to develop automations using legacy systems:
- Selenium IDE: If you are just starting your RPA automation project, we recommend that you use Power Automate for desktop instead.
- Windows recorder (V1): From November 30th, desktop flows will no longer be supported. Migrate your flows to Power Automate for desktop or delete them.
Follow these steps to create a simple Selenium flow.
Create a Selenium IDE flow
Sign in with your work or school account if needed.
Select My flows > Desktop flows > New.
Click Additional desktop flow options.
Select Selenium IDE, and then select Next.
Enter a name for your Selenium IDE flow into the Flow name field.
Enter the URL for the Website you want to automate into the Base URL field, and then select Launch recorder.
The Selenium IDE launches.
Tip: You can record actions across multiple HTTP or HTTPS websites within the same tab.
In Selenium IDE, select the red REC button in the top right side of the screen to launch the recorder.
The URL you chose in the previous step opens.
Perform the actions that you want to record on the website.
At the bottom right, you can see the recording status.
When you are finished recording, select on the red Stop button in the top right corner of the Selenium IDE.
Select the Run current test button from the top left side of the screen to see the Selenium IDE flow you just created run.
You can set the wait time between steps to slow the local playback for testing. This setting is for testing purposes only and has no impact when your Selenium IDE flow is deployed.
Select the Save project button in the top right of the Selenium IDE. This closes, and then uploads the project.
Now that you've created a Selenium IDE flow, use it in your other flows.
Limitations and known issues for Selenium IDE flows
Passwords in Selenium IDE are stored in plain text.
Temporary user profile for playback
Selenium IDE recordings are done with the current user's profile, but playback is done using a temporary user profile. This means that websites that need authentication may not ask for credentials during a recording session, but the authentication steps will be needed during playback.
To address this, the user needs to manually edit the script to insert the commands needed for the login process.
Recording desktop applications during a Web recording session. If you need to automate both Web and Desktop applications, you can create a separate desktop flows for each type and then combine them in a cloud flow.
Multi-Factor Authentication (MFA) is not supported, use a tenant that doesn't require MFA.
These Selenium IDE commands are not supported: Run, AnswerOnNextPrompt, ChooseCancelOnNextConfirmation, ChooseCancelOnNextPrompt, ChooseOkOnNextConfirmation, Debugger, ClickAt, DoubleClickAt, Echo, MouseOut, MouseUpAt, and MouseDownAt.
Selenium IDE actions or steps cannot exceed one minute to run. Use Power Automate instead.
Right click is not supported.
Additional Selenium IDE flow input is generated when you use Foreach commands. To work around this issue, input any value into the extra fields. It doesn't impact the playback.
If the .side file contains multiple test projects, only the first one that was created runs.
Note that the Selenium IDE orders the tests by name, not by creation date, so the first test created may not be the first one in the list.
Playback directly in the Selenium IDE might not behave as intended. However, playback at runtime behaves correctly.