Linking Mux 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.

Contents
This source is currently in alpha. The interface and available tables may change.
The Mux connector syncs your Mux Video data into the PostHog Data warehouse, so you can analyze your assets, live streams, and uploads alongside your product data.
Prerequisites
You need a Mux account with admin access so you can create an access token. Tokens are scoped to a single Mux environment.
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 Mux, you'll need:
- Access Token ID – create an access token under Settings → Access Tokens in your Mux dashboard.
- Secret Key – shown alongside the Access Token ID when you create the token. Grant Mux Video (read) for assets, live streams, uploads, playback restrictions, and transcription vocabularies, and Mux System (read) for signing keys.
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.
All Mux tables are full refresh only, since the API exposes no incremental sync filter.
Configuration
| Option | Type | Required |
|---|---|---|
Access Token ID | text | Yes |
Secret Key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
assets | A Mux Video Asset: an encoded piece of video or audio ready for streaming. | Full refresh | — | — |
live_streams | A Mux Video Live Stream: a configured RTMP/SRT ingest endpoint that produces Assets. | Full refresh | — | — |
uploads | A Mux Video Direct Upload: an authenticated URL for pushing source media directly to Mux. | Full refresh | — | — |
playback_restrictions | A Mux Video Playback Restriction: rules controlling where and how videos can be played. | Full refresh |