Linking Browser Use as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
This source is currently in alpha. The interface and available tables may change.
Browser Use Cloud runs hosted AI browser-automation agents. This connector syncs your agent sessions, browser sessions, profiles, workspaces, and per-session agent messages into the PostHog Data warehouse, so you can analyze agent runs, step counts, token usage, and costs alongside the rest of your data.
Prerequisites
You need a Browser Use Cloud account with an API key. Keys are created self-serve and don't expire.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
When linking Browser Use, you'll need:
- API key – create one at cloud.browser-use.com/settings. Keys are prefixed
bu_.
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
Browser Use's v3 list endpoints don't support server-side time filtering, so every table syncs with full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
sessions | A hosted agent run on Browser Use Cloud, with its status, model, step count, token usage, and per-run costs. | Full refresh | — | — |
browser_sessions | A hosted browser instance backing agent runs, with its start/finish timestamps, proxy usage, and costs. | Full refresh | — | — |
profiles | A reusable browser profile that persists cookies and browsing state across agent sessions. | Full refresh | — | — |
workspaces | A workspace that groups agent sessions and their associated files. | Full refresh | — | — |
session_messages | Individual agent steps/messages within a session, in the order they occurred. | Full refresh | — | — |
The session_messages table fans out one request per session, so it's off by default. Enable it only if you need per-step agent messages, since it makes many more API calls than the session-level tables.
Troubleshooting
- If the connection fails with an authentication error, confirm the API key is valid and hasn't been revoked in your Browser Use account settings, then reconnect.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.