Skip to main content
Browser commands enable you to automate web browser interactions including opening pages, clicking elements, filling forms, and extracting content. These commands are essential for web scraping and browser-based automation workflows.

Overview

Browser commands provide functionality for:
  • Opening and navigating web pages
  • Interacting with DOM elements (clicks, inputs, scrolling)
  • Extracting text content and attributes
  • Managing browser sessions
  • Handling dynamic content and JavaScript-rendered pages

Available Commands

Browser Open

Navigate the browser to a URL and wait for a navigation event (ID 2)

Click by Javascript

Select DOM elements by locator and click them via element.click() (ID 3)

Get Text Contents

Extract text content from DOM elements (ID 4)

Get Attributes

Extract attributes from DOM elements for detailed scraping operations (ID 5)

Wait For DOM Element

Wait for specific DOM elements to appear in the browser (ID 6)

Get Window Data

Retrieve and optionally map data from the browser window object (ID 7)

Get Elements

Retrieve DOM elements and return their detailed representations (ID 8)

Get Inner Texts

Retrieve the visible inner text of specified DOM elements (ID 9)

Run Custom Code

Execute custom JavaScript code in the browser context (ID 10)

Subscribe WebSocket Event

Subscribe to a WebSocket instance in the browser window context to monitor real-time messages (ID 11)

Observe Property

Monitor changes to a specified property in the browser window object (ID 12)

Listen

Subscribe to DOM events in the browser window and relay event details via push callbacks (ID 13)

Get Window Data Simple

Retrieve a window object property using a simple dot-separated path (ID 14)

Clear Browsing Data

Remove specified types of browsing data from the browser (ID 15)

Override Headers

Modify HTTP headers for outgoing network requests in the browser (ID 16)

Set Window Data

Set a value at a given path within the browser window object (ID 17)

Web Request

Listen for and intercept HTTP requests made by the browser at various lifecycle stages (ID 18)

Get Web Data

Execute an HTTP request from within the browser context using the fetch API (ID 19)

Get Page Rectangle

Get the bounding rectangle dimensions of the current browser page (ID 20)

Override Document Functions

Override native document prototype functions to intercept or manipulate their behavior (ID 21)

Get Elements Positions

Retrieve positions and bounding rectangles of DOM elements identified by a CSS selector (ID 22)

Capture HAR File

Capture a HAR (HTTP Archive) file from the browser recording all network activity (ID 23)

Fetch Web Request

Send a web request using the browser fetch API (ID 24)

Get Full Elements Positions

Retrieve element positions along with browser window, screen, and document resolution details (ID 25)

Parallel Fetch Web Request

Send multiple web requests in parallel using the browser fetch API (ID 26)

Switch Timezone (Browser)

Set the timezone of the OS on the browser machine (ID 998)

Switch Proxy (Browser)

Switch proxy settings for the browser scraper (ID 999)

Common Use Cases

  • Web Scraping: Extract content from web pages
  • Form Automation: Automate form filling and submission
  • Dynamic Content: Handle JavaScript-rendered content
  • Multi-Page Navigation: Navigate through multiple pages
  • Content Extraction: Extract text, links, and attributes from pages

Browser Session

Each Browser step runs in a browser provided by its Technology Used (Chrome, Chrome headless, Firefox or Android). All Browser commands in the step share that browser, so there is no session parameter to pass: navigate with Browser Open, then extract or interact.

Common Parameters

Element Locators

Browser commands use element locators to target specific DOM elements:

CSS Selectors

Advanced Locator Features

  • Filtering: Filter by innerText, hasChildren, or index
  • Chained Locators: Use continueWith for nested searches
  • Multiple Elements: Returns arrays for multiple matching elements

Best Practices

  • Set Appropriate Timeouts: Configure timeouts for dynamic content loading
  • Wait for Elements: Ensure elements are loaded before interaction
  • Handle Dynamic Content: Account for JavaScript-rendered content
  • Use Descriptive Selectors: Use clear, stable CSS selectors