Linking Linode 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.
This source is currently in alpha. The interface and available tables may change.
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
- 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 Linode, you'll need:
- Personal access token – create one in the Linode Cloud Manager 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_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.
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 | — |
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.