ExamFinch.com My Study

Study guide

9.1 Browser Automation with the WebDriver Protocol

Practice this exam

UiPath Automation Developer Professional UiPath-ADPv1

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Blueprint Map

1.1 About the UiPath-ADPv1 Exam: Format, Fees & Policies 1.2 The Exam Topics Mapped to This Guide & a Study Plan

2 Chapter 2: REFramework Architecture & State Dynamics

2.1 State Machine Architecture & The Four Core States 2.2 Configuration Management: Settings, Constants, and Assets 2.3 Transaction Types & The Dispatcher vs. Performer Architecture 2.4 Adapting REFramework: Tabular Data, Collections & Linear Processes

3 Chapter 3: REFramework Exception Handling & Recovery

3.1 BusinessRuleException vs. System.Exception Handling Patterns 3.2 Retry Mechanisms: Queue Retries vs. REFramework MaxRetryNumber 3.3 Consecutive System Exceptions & Graceful Process Termination

4 Chapter 4: State Machines, Custom Log Fields & REFramework Testing

4.1 Building State Machine Projects in Studio 4.2 Logging Levels, Robot Logs & Custom Log Fields in REFramework 4.3 Testing a REFramework Project With and Without Orchestrator Queues

5 Chapter 5: LINQ Queries & DataTable Operations

5.1 LINQ Essentials for Collections & Filtering 5.2 Advanced DataTable Querying with LINQ 5.3 In-Memory DataTable Transformations & Column Operations

6 Chapter 6: Regex, DateTime, JSON & Invoke Activities

6.1 Regular Expressions & Text Parsing for Automation 6.2 DateTime Formatting, Timezone Conversions & TimeSpan Calculations 6.3 JSON Parsing, JSONPath & Serialization with Newtonsoft.Json 6.4 Invoke Method & Invoke Code Activities 6.5 Data Referencing in Invokes: DataTable, List & Dictionary Arguments

7 Chapter 7: Modern UI Automation & Unified Targeting

7.1 Modern Design Experience & The Unified Target Concept 7.2 Anchors, Relative Elements & UI Automation Activities 7.3 Dynamic Selectors, Variables & Wildcards in Selectors

8 Chapter 8: Object Repository, Computer Vision & Remote Runtime

8.1 Object Repository & UI Descriptor Libraries 8.2 AI Computer Vision for Unattended & Remote Interfaces 8.3 Automation in Virtual Environments & UiPath Remote Runtime

9 Chapter 9: Advanced UI Automation: Browser Modes, Agentic UI & macOS

9.1 Browser Automation with the WebDriver Protocol 9.2 Agentic UI Automation: ScreenPlay, Semantic Activities & Healing Agent 9.3 macOS Automation: Native Apps, Office Apps & AppleScript

10 Chapter 10: Advanced Control Flow & Exception Architecture

10.1 Flowcharts, Sequences & Parallel Control Flow Patterns 10.2 Global Exception Handler Architecture & ErrorAction Directives 10.3 TryCatch, Retry Scope & Custom Exception Architectures

11 Chapter 11: Orchestrator Queues & Transaction Management

11.1 Queue Architecture, SpecificContent & Transaction Lifecycles 11.2 Queue Items SLA, Postpone, Deadlines & Priority Scheduling 11.3 Bulk Operations, Transaction Status Updates & Queue Triggers

12 Chapter 12: Orchestrator Tenant & Folder Entities

12.1 Asset Types, Per-Robot Assets & External Credential Stores 12.2 Modern Folder Hierarchy, User/Robot Assignment & Permissions 12.3 Storage Buckets, Webhooks & Environment Promotion 12.4 Orchestrator Tags: Labels, Properties & Governance

13 Chapter 13: Unattended Execution, API Triggers & Cloud Robots

13.1 Unattended Job Execution: Folders, Priorities, Background vs. Foreground & Runtimes 13.2 API Triggers: Starting Jobs from External Systems over HTTP 13.3 Serverless and Cloud VM Robots: Cloud-Hosted Execution Options

14 Chapter 14: Monitoring, Recording & Solutions Management

14.1 Orchestrator Monitoring, Trigger Alerts & Job Health 14.2 Job and Transaction Recording: Troubleshooting Faulted Unattended Jobs 14.3 Solutions Management: Packaging and Deploying Automations with Their Resources

15 Chapter 15: Debugging, Remote Debugging & Profiling

15.1 Studio Debugging Tools: Breakpoints, Panels & Execution Control 15.2 Remote Debugging: Remote Machine and Unattended Robot Connections 15.3 Profile Execution: Finding Performance Bottlenecks in Studio

16 Chapter 16: RPA Testing & Test Suite

16.1 UiPath Test Suite Overview, Test Cases & Given-When-Then Structure 16.2 Data-Driven Testing, Test Verification Activities & Mock Activities 16.3 CI/CD Pipelines with uipcli & Test Manager Traceability

17 Chapter 17: Long-Running Workflows, Action Center & Apps

17.1 Long-Running Workflows: Persistence, Suspend and Resume 17.2 Action Center & Human-in-the-Loop Orchestration 17.3 UiPath Apps: Action Apps, Automations & Integration Service

18 Chapter 18: Trigger-Based Attended Automation & Callouts

18.1 Trigger-Based Attended Automation: Forms, Triggers & Global Variables 18.2 Running Local Triggers & the Event Inspection Tool 18.3 Callouts & Forms for Attended Guidance

19 Chapter 19: UiPath Assistant & Robot Sessions

19.1 UiPath Assistant: Automations, Reminders, Widgets & Configuration 19.2 Robot Session (Picture in Picture): Child Session vs. Virtual Desktop

20 Chapter 20: Autopilot for Developers & Autopilot for Everyone

20.1 Autopilot for Developers: AI Assistance in Studio and Studio Web 20.2 Autopilot for Everyone: Chat, Automations & Clipboard AI

21 Chapter 21: API Automation & Integration Service

21.1 Integration Service: Connectors, Connections & Connector Activities 21.2 API Workflows in Studio Web 21.3 HTTP Requests: Web APIs, the Orchestrator API & Connector Requests 21.4 Connector Builder: Custom Integration Service Connectors 21.5 Integration Service Event Triggers: Connected and Disconnected 21.6 GenAI Activities: Generative AI Inside Workflows

22 Chapter 22: Data Service, Context Grounding & Coded Workflows

22.1 Data Fabric (Data Service) Entities: Modeling Business Data 22.2 Data Fabric Activities and the Platform Connector 22.3 Context Grounding: Retrieval-Augmented Generation with Company Data 22.4 Coded Automations: Structure, Arguments & Invoking Workflows 22.5 Coded Automation Services: Orchestrator, UI Automation, Microsoft 365 & Custom Services

23 Chapter 23: Integrated Scenario Practice

23.1 Integrated Scenario Practice: Designing an End-to-End Solution

9.1 Browser Automation with the WebDriver Protocol

Key Takeaways Explain This Topic AI

WebDriver automations in UiPath work with Chrome, Firefox, and Edge, need the matching driver executable (ChromeDriver, geckodriver, msedgedriver) on the Path, and need no UiPath extension.

Selectors generated through WebDriver are the same as those from the UiPath extensions, except for window frames.

The Browser automation mode setting offers Browser Extension (default), WebDriver with GUI, WebDriver Headless, Chromium Automation, and Chromium Automation Headless.

WebDriver and Chromium modes open a new, isolated browser profile, so they cannot attach to a user's open browser and are unsuitable for attended automation.

Headless modes cannot perform hardware drag-and-drop or some screenshot operations; ChromeDriver must match the installed Chrome version.

Last updated: September 2026

9.1 Browser Automation with the WebDriver Protocol

Core Concept: By default, UiPath automates browsers through its browser extension . The exam description also asks you to "build a UI automation using Web Driver". The W3C WebDriver protocol lets the robot drive Chrome, Edge, or Firefox through a separate driver executable. It needs no UiPath extension, and it supports a headless mode in which no browser window is drawn at all.

How WebDriver Works in UiPath

WebDriver is a widely used protocol that exposes a REST API in an executable separate from the browser itself. Through it, a client can start browsers (headless or visible), click elements, type into fields, open tabs, read the DOM, and run JavaScript. In UiPath:

Automations can use WebDriver with Google Chrome , Mozilla Firefox , and Microsoft Edge .

No UiPath browser extension is required, but the matching driver executable is: ChromeDriver.exe , geckodriver.exe , or msedgedriver.exe .

Selectors generated through WebDriver are the same as those generated through the UiPath extensions, except for window frames.

Each WebDriver run opens a new browser session that is independent of any browser the user already has open. When the browser closes, the driver process and its sessions end too.

Setting It Up

Download the driver that matches the browser. ChromeDriver must match the installed Chrome version, and because Chrome updates itself often, the driver must be kept in step. geckodriver changes rarely; use the latest release.

Put the driver in a folder , such as C:\webdriver\Chrome .

Add that folder to the Path environment variable (user or system) through Windows' Edit the system environment variables dialog.

Choose the mode in Studio. In current UIAutomation packages (v26.10 and later), Use Application/Browser has a Browser automation mode property, and the project setting of the same name is in UI Automation Modern > Application/Browser . The activity-level value overrides the project default.

The Browser Automation Modes

UiPath describes three underlying methods exposed as five modes:

  • Mode Needs extension Needs WebDriver binary Visible window Supported browsers Attended use
  • Browser Extension (default) Yes No Yes Chrome, Edge, Firefox, Safari Yes
  • WebDriver with GUI No Yes Yes Chrome, Edge, Firefox No
  • WebDriver Headless No Yes No Chrome, Edge, Firefox No
  • Chromium Automation No No Yes Chrome, Edge, other Chromium browsers No
  • Chromium Automation Headless No No No Chrome, Edge, other Chromium browsers No

The two Chromium Automation modes use the Chrome DevTools Protocol directly, so no extension or driver download is needed. They are blocked when the DeveloperToolsAvailability Group Policy is set to 2 , which disallows Developer Tools. In that environment, use the extension or WebDriver instead.

Why WebDriver and Chromium Modes Are Unattended-Only

WebDriver and Chromium Automation create a new user-data directory for every session. As a result:

They cannot attach to a browser the user already has open , which makes them unsuitable for attended automation, where the robot works in the user's own browser.

The session uses an isolated profile , so extensions, saved passwords, and session cookies from the user's normal profile are not available. Log in inside the automation.

Incognito or private browsing works without extra configuration, unlike with the extension, where you must allow the extension in Incognito.

For unattended jobs these points are rarely a problem, and headless modes are attractive on servers and in CI/CD pipelines where no display exists.

Headless Limitations

Headless modes skip everything that needs a visible window or OS-level rendering:

Hardware events such as a physical mouse drag-and-drop are not supported.

Some screenshot operations do not work.

Image and Computer Vision targeting have no rendered screen to analyze, so rely on selectors.

A practical pattern is to build and debug with WebDriver with GUI , where you can watch the page, and then switch the same Use Application/Browser activity to WebDriver Headless for production.

Choosing a Mode

  • Scenario Recommended mode
  • Standard desktop automation where the extension can be installed Browser Extension
  • Attended automation in the user's already-open browser Browser Extension
  • Extension cannot be installed, and the browser must be visible WebDriver with GUI
  • Extension cannot be installed, and no display is available WebDriver Headless
  • Firefox or Safari without the extension WebDriver (with GUI or headless)
  • Chrome or Edge with the simplest setup Chromium Automation
  • Unattended server or pipeline runs on Chrome or Edge Chromium Automation Headless

Warning

A WebDriver automation that suddenly fails after a Chrome update usually has a version mismatch between Chrome and ChromeDriver. Keep the driver in step with the browser, or use Chromium Automation, which has no separate binary to maintain.