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

# Linking Hetzner Cloud as a source

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

> **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 Hetzner Cloud connector syncs servers, volumes, load balancers, and more into the PostHog data warehouse, so you can analyze them alongside your product data.

## Prerequisites

Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.

## 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.

Enter a Hetzner Cloud API token to sync your Hetzner Cloud project.

Create a token under **Security > API tokens** in the [Hetzner Cloud Console](https://console.hetzner.cloud/). A `Read` token is enough. Each token is scoped to a single project, so connect one source per project you want to sync.

You'll be asked for:

-   **API token**

## 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.

All Hetzner Cloud tables are full refresh. Each sync replaces the contents of the table.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API token` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `servers` | Cloud servers (virtual machines) in the project. | Full refresh | — | — |
| `volumes` | Block storage volumes that can be attached to servers. | Full refresh | — | — |
| `load_balancers` | Load balancers distributing traffic across targets. | Full refresh | — | — |
| `networks` | Private networks connecting servers within the project. | Full refresh | — | — |
| `firewalls` | Firewalls with inbound/outbound rules applied to resources. | Full refresh | — | — |
| `images` | Images (system, snapshot, backup, or app) available to create servers from. | Full refresh | — | — |
| `floating_ips` | Floating IPs that can be assigned between servers. | Full refresh | — | — |
| `primary_ips` | Primary IPs bound to servers. | Full refresh | — | — |
| `certificates` | TLS certificates (managed or uploaded) for use with load balancers. | Full refresh | — | — |
| `ssh_keys` | SSH public keys that can be injected into new servers. | Full refresh | — | — |
| `placement_groups` | Placement groups controlling how servers are spread across physical hosts. | Full refresh | — | — |
| `actions` | Append-only history of every operation performed in the project (create, delete, attach, etc.). | Full refresh | — | — |
| `server_types` | Catalog of available server types with their resources and pricing. | Full refresh | — | — |
| `load_balancer_types` | Catalog of available load balancer types with limits and pricing. | Full refresh | — | — |
| `datacenters` | Catalog of datacenters and the server types available in each. | Full refresh | — | — |
| `locations` | Catalog of locations (cities/regions) where resources can be created. | Full refresh | — | — |
| `isos` | Catalog of ISO images that can be mounted to servers. | Full refresh | — | — |
| `zones` | DNS zones managed in the project. | Full refresh | — | — |
| `pricing` | Current prices for every resource kind, in the project owner's currency and VAT rate. One row. | Full refresh | — | — |
| `server_metrics` | CPU, disk and network time series per server, at a 5-minute resolution. The API keeps 30 days. | Incremental, Full refresh | timestamp | — |
| `load_balancer_metrics` | Connection, request and bandwidth time series per load balancer, at a 5-minute resolution. The API keeps 30 days. | Incremental, Full refresh | timestamp | — |
| `network_members` | Servers and load balancers attached to each private network, with their IP inside the network. | Full refresh | — | — |
| `zone_rrsets` | DNS resource record sets (RRSets) of each zone. One row per record name and type. | Full refresh | — | — |

## Troubleshooting

-   If the connection fails with an authorization error, the API token is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
-   If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.

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.