> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking RunPod as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/runpod

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

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.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

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

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#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 RunPod, you'll need:

-   **API key** – create one under **Settings → API Keys** in the [RunPod console](https://console.runpod.io/user/settings). 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_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](https://posthog.com/docs/data-pipelines/sources.md#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](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.