Linking Baserow as a source

The Baserow connector syncs the tables from your Baserow databases into the PostHog data warehouse, so you can query your no-code data alongside your product data. Each Baserow table becomes its own warehouse table, with your field names as columns.

It works with both Baserow's hosted service at baserow.io and self-hosted Baserow instances.

Prerequisites

You need:

• A Baserow database token. Create one in Baserow under Settings > Database tokens, and enable read permission for the databases or tables you want to sync.
• For self-hosted Baserow: an instance reachable over HTTPS from the internet. Plain http:// instance URLs are not supported.

Adding a data source

1. In PostHog, go to the Sources tab of the data pipeline section.
2. Click + New source and click Link next to this source.
3. Enter your credentials (see Configuration below) and click Next.
4. 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 Baserow, provide:

1. Database token: the token created above.
2. Instance URL (optional): your self-hosted Baserow host, e.g. https://baserow.example.com. Leave it blank to use Baserow's hosted service.

PostHog then lists every table your token can see, across all databases in its workspace. Tables without read permission on the token are flagged in the picker, so you can either deselect them or enable read access in Baserow's token settings.

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_at timestamp). 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.

Baserow's row listing API has no server-side "updated since" filter, so every table syncs as a full refresh. Rows are fetched with your field names as column names, plus the row's id and order.

Configuration

Supported tables

The tables available from this source are discovered from your account when you connect it, so the exact list depends on your data. Once connected, you can pick which tables to sync from the sources tab.

Troubleshooting

• Invalid Baserow database token: the token doesn't exist or has been revoked. Create a new database token in Baserow and reconnect.
• A table fails to sync with a permission error: the token's read toggle is off for that table. In Baserow, open Settings > Database tokens and enable read access for the table, then re-run the sync.
• A table stops syncing after being renamed: renames are fine for existing syncs (PostHog tracks the underlying table id), but the table appears under its new name when you add new schemas.

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.