Linking Kernel as a source
This source is currently in alpha. The interface and available tables may change.
Kernel is browser infrastructure for AI agents. This connector syncs your Kernel apps, deployments, action invocations, cloud browser sessions, and saved profiles into the PostHog data warehouse so you can join agent run history with your product data.
Prerequisites
A Kernel account with an API key. Kernel API keys are long-lived and grant organization-wide read access.
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.
You need a Kernel API key. Create one in your Kernel dashboard under API keys, then paste it into the connection form.
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.
Kernel tables sync in full-refresh mode. Incremental sync is not yet available for this connector.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
apps | Deployed browser-automation apps registered in your Kernel organization. | Full refresh | — | — |
deployments | Deployment history for your apps, including status and region. | Full refresh | — | — |
invocations | Action run history: status, payload, output, and start/finish timestamps. | Full refresh | — | — |
browsers | Cloud browser sessions, including active and soft-deleted sessions. | Full refresh | — | — |
profiles | Saved browser profiles (persisted cookies, storage, and auth state). | Full refresh | — | — |
Troubleshooting
If the connection fails with an authentication error, confirm the API key is active in your Kernel dashboard and has not been revoked. Kernel enforces per-organization rate limits, so very large syncs may take longer while the connector backs off and retries.
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.