Browserless
Everruns integrates with Browserless to provide cloud-based browser automation. Agents can navigate web pages, take screenshots, read DOM content, scrape structured data, and interact with UI elements (click, type, keyboard, mouse, touch).
What You Get
Section titled “What You Get”- Screenshots: Capture full-page or element-specific PNG screenshots
- DOM Reading: Get fully rendered HTML including JavaScript-generated content
- Structured Scraping: Extract data from pages using CSS selectors
- Browser Interactions: Click, type, press keys, use mouse/touch events
- Persistent Sessions: Keep a browser alive across tool calls for login-protected pages (CDP mode)
Quick Start
Section titled “Quick Start”1. Get Your API Token
Section titled “1. Get Your API Token”- Go to the Browserless Dashboard
- Navigate to API Keys in your account settings
- Copy your API token
2. Connect in Everruns
Section titled “2. Connect in Everruns”- Go to Settings > Connections
- Find Browserless in the available providers
- Click Connect and paste your API token
Once connected, the Browserless capability is automatically available in agent sessions.
3. Use in Sessions
Section titled “3. Use in Sessions”Agents with the Browserless capability can use these tools:
| Tool | Description |
|---|---|
browserless_open_browser | Open a persistent browser session (CDP mode) |
browserless_close_browser | Close the persistent browser session |
browserless_navigate | Navigate to a URL and get page metadata |
browserless_screenshot | Take a PNG screenshot of a page |
browserless_content | Get the fully rendered HTML/DOM content |
browserless_scrape | Extract structured data via CSS selectors |
browserless_interact | Multi-step interactions (click, type, keyboard, mouse, touch) |
Two Operating Modes
Section titled “Two Operating Modes”Stateless Mode (Default)
Section titled “Stateless Mode (Default)”Each tool call launches a fresh browser that is destroyed after the response. No state persists between calls. Best for one-shot operations like screenshots or scraping.
Persistent Session Mode (CDP)
Section titled “Persistent Session Mode (CDP)”Use browserless_open_browser to create a persistent browser via Chrome DevTools Protocol. The browser stays alive between tool calls, preserving login state, cookies, and navigation history. Use browserless_close_browser when done.
Example workflow for login-protected pages:
browserless_open_browserwith the login page URLbrowserless_interactto fill credentials and submit the formbrowserless_navigateto browse authenticated pagesbrowserless_screenshotto capture authenticated page statebrowserless_close_browserto release resources
Use Cases
Section titled “Use Cases”- Accessibility testing — Navigate pages, read DOM, check ARIA attributes and heading structure
- Regression testing — Screenshot pages and verify content after changes
- Login flows — Use persistent sessions to authenticate and test protected pages
- Web scraping — Extract structured data from any website
- Visual QA — Take before/after screenshots to verify UI changes
Resource Management
Section titled “Resource Management”- Stateless mode: No cleanup needed — browsers are ephemeral
- CDP mode: Browsers auto-expire after 60 seconds of inactivity. Always call
browserless_close_browserwhen done for immediate cleanup.
Security
Section titled “Security”- API tokens are encrypted at rest (AES-256-GCM envelope encryption)
- Browser sessions are fully isolated on Browserless servers
- CDP session state stores only the WebSocket endpoint (no secrets), scoped per session
- Large DOM responses are truncated to 100KB to prevent context flooding