Linking 100ms 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.
The 100ms connector syncs your video conferencing data – sessions, recordings, and live streams – into the PostHog data warehouse, so you can analyze call activity alongside your product data.
Prerequisites
You need a 100ms account with access to the Developer section of your 100ms dashboard. You'll need an app access key and app secret to authenticate.
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 100ms, you'll need:
- App access key – find it in the Developer section of your 100ms dashboard.
- App secret – find it in the same Developer section, alongside the app access key.
Sync behavior
Only completed sessions are imported. Active (in-progress) sessions are excluded until they finish.
The sessions table uses a 24-hour lookback window for incremental sync. This re-reads recent sessions to catch calls that were still in progress when the previous sync ran. Older corrections require a full refresh.
Recordings and live streams use full refresh only, since the 100ms API doesn't provide time-bound filters for these endpoints.
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 |
|---|---|---|
App access key | password | Yes |
App secret | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
sessions | Completed calls in 100ms rooms, with the peers who joined each call. | Incremental, Full refresh | created_at | — |
recordings | Recording jobs for the workspace. The list excludes recording assets. | Full refresh | — | — |
live_streams | Live stream jobs for the workspace, including their status and playback details. | Full refresh | — | — |
Troubleshooting
- If you get an authentication error, check that your app access key and app secret are correct and haven't been rotated in your 100ms dashboard.
- If you get a permission error, verify that your credentials have read access to the workspace.
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.