Create and test your Web UI flows

Follow these steps to create a simple Web UI flow.

Create a Web UI flow

  1. Open the Microsoft Edge (version 80 or later) or Google Chrome, and then navigate to Power Automate.

  2. Sign in with your work or school account if needed.

  3. Select My flows > UI flows > New.

    Create new UI flow

  4. Select Web app > Next

    Select Web app

  5. Enter a name for your UI flow into the Flow name field.

  6. Enter the URL for the Website you want to automate into the Base URL field, and then select Launch recorder.

    Give a name and a URL

    The Selenium IDE launches.

    Tip

    Tip: You can record actions across multiple HTTP or HTTPS websites within the same tab.

  7. 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.

    Select Rec

  8. Perform the actions that you want to record on the website.

    Tip

    At the bottom right, you can see the recording status.

    Recording status

  9. When you are finished recording, select on the red Stop button in the top right corner of the Selenium IDE.

    Stop button

  10. Select the Run current test button from the top left side of the screen to see the UI flow you just created run.

    Run current test

    Tip

    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 UI flow is deployed.

  11. 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 Web UI flow, use it in your other flows.

Limitations and known issues for Web UI flows

Warning

Passwords in Selenium IDE are stored in plain text.

UI flows no longer records or plays back Windows applications after installing a new version.

Confirm you are using the latest version

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.

Other limitations

  • Recording desktop applications during a Web recording session. If you need to automate both Web and Desktop applications, you can create a separate UI flows for each type and then combine them in a 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.

  • Right click is not supported.

  • Additional Web UI 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.

    Tip

    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 through the UI flow infrastructure behaves correctly.

Next steps