Linking RunPod as a source
This source is currently in alpha. The interface and available tables may change.
The RunPod connector syncs your GPU cloud infrastructure – Pods, Serverless endpoints, templates, and network volumes – plus daily billing history into PostHog, so you can analyze compute spend alongside your product data.
Prerequisites
You need a RunPod account and an API key. A key with read permission is sufficient.
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 RunPod, you'll need:
- API key – create one under Settings → API Keys in the RunPod console. The key grants read access to your Pods, endpoints, templates, network volumes, and billing history.
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.
The billing tables support incremental syncs: each run picks up new day buckets from where the last one stopped and re-reads a trailing window so recently restated charges stay accurate. The infrastructure tables (Pods, endpoints, templates, and network volumes) are snapshots and sync with full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
pods | GPU and CPU Pods in your RunPod account, including on-demand instances and Serverless workers. | Full refresh | — | — |
endpoints | Serverless endpoints in your RunPod account, including autoscaling configuration. | Full refresh | — | — |
templates | Pod and Serverless templates in your RunPod account. | Full refresh | — | — |
network_volumes | Network volumes in your RunPod account, attachable to Pods and Serverless endpoints. | Full refresh | — | — |
billing_pods | Daily billing history for Pods, one record per Pod per day bucket. | Incremental, Full refresh | time | — |
billing_endpoints | Daily billing history for Serverless endpoints, one record per endpoint per day bucket. | Incremental, Full refresh | time | — |
billing_network_volumes | Daily billing history for network volume storage, aggregated account-wide per day bucket. | Incremental, Full refresh | time | — |
Troubleshooting
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.