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

# Linking Linode as a source

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

> **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)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](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

Sync your Linode (Akamai Connected Cloud) account data — infrastructure inventory, billing history, and audit events — into the PostHog data warehouse to join it with your product data.

## Prerequisites

You need a Linode account with permission to create a personal access token. Grant read-only access to the resources you want to sync.

## 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 Linode, you'll need:

-   **Personal access token** – create one in the [Linode Cloud Manager](https://cloud.linode.com/profile/tokens) under **Profile → API Tokens**. Grant **read-only** access to the resources you plan to sync (Account, Linodes, Volumes, NodeBalancers, Kubernetes, Domains).

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

Account events sync in append-only mode (an immutable audit log; the Linode API only retains the last 90 days). Invoices sync incrementally by date. Infrastructure inventories (linodes, volumes, nodebalancers, LIKE clusters, domains, users, payments) use full refresh.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Personal access token` | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `linodes` | Linode instances (virtual machines) on the account. | Full refresh | — | — |
| `volumes` | Block storage volumes on the account. | Full refresh | — | — |
| `nodebalancers` | NodeBalancers (managed load balancers) on the account. | Full refresh | — | — |
| `lke_clusters` | Linode Kubernetes Engine (LKE) clusters on the account. | Full refresh | — | — |
| `domains` | DNS domains (zones) managed by the account's DNS Manager. | Full refresh | — | — |
| `users` | Users with access to the Linode account. | Full refresh | — | — |
| `invoices` | Billing invoices issued to the account. | Incremental, Full refresh | date | — |
| `payments` | Payments made against the account. | Full refresh | — | — |
| `events` | Account audit events (the last 90 days of activity). Immutable and append-only. | Append only, Full refresh | id | — |
| `invoice_items` | Line items on each billing invoice, breaking the invoice total down by service. | Full refresh | — | — |
| `account_transfer` | Network transfer pool usage for the current billing cycle. One row, replaced on every sync. | Full refresh | — | — |
| `linode_types` | Linode plan types with their specs and prices. Joins to the type column on linodes. | Full refresh | — | — |
| `regions` | Regions (data centers) where resources can be deployed. Joins to the region column on other tables. | Full refresh | — | — |
| `images` | Disk images available to the account: private images (manual or automatic recovery images) and public distribution images. | Full refresh | — | — |
| `databases` | Managed Database clusters on the account, for every engine (MySQL, PostgreSQL and Valkey). | Full refresh | — | — |
| `database_types` | Managed Database node plan types with their specs and prices per engine. Joins to the type column on databases. | Full refresh | — | — |
| `lke_node_pools` | Node pools of the LKE (Kubernetes) clusters on the account, with their size and autoscaling settings. | Full refresh | — | — |
| `linode_monthly_transfer` | Public network transfer of each Linode per calendar month. The row for the current month covers the past 30 days and changes until the month ends. | Incremental, Full refresh | month\_start | — |
| `volume_quotas` | Block Storage (Volumes) quotas applied to the account, with the maximum allowed per region or globally. | Full refresh | — | — |
| `volume_quota_usage` | Current usage of each Block Storage (Volumes) quota on the account. Quotas without usage data have no row. | Full refresh | — | — |

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