Capabilities
Five Actions. Infinite Possibilities.
👆
Click
Click any element
📋
Extract
Pull text & data
📸
Screenshot
Capture state
Example
Extract Data from a Legacy System
No API? No problem. Here's how browser automation integrates a legacy CRM that only has a web interface.
browser_automation:
actions:
- type: navigate
url: "https://legacy-crm.company.com/login"
- type: fill
selector: "#username"
value: "{{credentials.username}}"
- type: fill
selector: "#password"
value: "{{credentials.password}}"
- type: click
selector: "button[type='submit']"
- type: click
selector: ".nav-reports"
- type: extract_text
selector: ".report-table"
output: "report_data"
Use Cases
When to Use Browser Automation
Legacy CRM Data Sync
Problem: CRM has no export API. Marketing needs lead data.
Solution: Browser automation logs in, navigates to exports, extracts data daily.
Government Portal Filings
Problem: Quarterly compliance requires navigating a terrible portal.
Solution: Browser automation handles login, navigation, and PDF download.
Competitor Price Monitoring
Problem: Need to track competitor pricing across 20 product pages.
Solution: Browser automation extracts prices every 4 hours, alerts on changes.
SaaS Tool Data Export
Problem: Tool only exports via email or manual download.
Solution: Browser automation clicks export, handles download, feeds to workflow.
Technology
Built on Playwright
Under the hood, browser automation runs on Playwright — the same framework used by Microsoft, Google, and Netflix for browser automation.
- Handles dynamic content and JavaScript-heavy sites
- Faster than Selenium, optimized for headless operation
- Cross-browser support (Chrome, Firefox, WebKit)
- Full-page and element screenshots for debugging
- Automatic waiting for elements to load
- Network interception for advanced use cases
Decision Guide
Browser Automation vs. Native Adapters
| Scenario |
Recommendation |
| Target system has no API |
Browser automation |
| Speed matters (1000+ ops/hour) |
Native adapter |
| Quick prototype before full integration |
Browser automation |
| Long-term, high-reliability integration |
Native adapter |
| API is rate-limited or expensive |
Browser automation (sometimes) |
| UI is the only stable interface |
Browser automation |
Reality check: Most enterprises need both. Native adapters for the 80% with good APIs. Browser automation for the 20% that don't.
Editions
Available in All Editions
| Feature |
Community |
Business |
Enterprise |
| Browser automation nodes |
✓ |
✓ |
✓ |
| 5 actions (navigate, click, fill, extract, screenshot) |
✓ |
✓ |
✓ |
| ML-enhanced element detection |
— |
✓ |
✓ |
| Credential vault integration |
— |
✓ |
✓ |
| Compliance audit trail on all actions |
— |
— |
✓ |
| IP allowlisting & rate controls |
— |
— |
✓ |