Linking Beamer as a source
This source is currently in alpha. The interface and available tables may change.
The Beamer connector syncs your changelog posts, feature requests, comments, votes, reactions, and NPS responses into the PostHog Data warehouse, so you can analyze product engagement and feedback alongside your product data.
Prerequisites
You need a Beamer account with access to your API key. Some tables have additional requirements: the Users table needs a Beamer Scale plan, and some post queries need the key's "Read posts (ignore filters)" permission.
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 Beamer, you'll need:
- API key – find it in your Beamer account settings. Beamer sends it in the
Beamer-Api-Keyheader.
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.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
posts | A changelog post / announcement (the notifications shown in the Beamer feed and widget). | Incremental, Full refresh | date | — |
feature_requests | An Idea / feature request submitted on the Beamer roadmap, with vote and comment counts. | Incremental, Full refresh | date | — |
nps | A Net Promoter Score (NPS) survey response, including the score and optional feedback. | Incremental, Full refresh | date | — |
users | Requires a Beamer Scale plan. Full refresh only | Full refresh | — | — |
post_comments | Full refresh only (fanned out over every parent record) | Full refresh | — | — |
post_reactions | Full refresh only (fanned out over every parent record) | Full refresh | — | — |
feature_request_comments | Full refresh only (fanned out over every parent record) | Full refresh | — | — |
feature_request_votes | Full refresh only (fanned out over every parent record) | Full refresh | — | — |
Troubleshooting
- If you see an authentication error, your API key may be invalid or revoked. Generate a new key in your Beamer account settings, then reconnect.
- If a table fails with a permission error, your key may be missing the plan or permission needed to sync it. The Users table needs a Scale plan, and some post queries need the "Read posts (ignore filters)" permission. Adjust the key in your Beamer 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.