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

# Linking DigitalOcean as a source

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

> **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 DigitalOcean connector syncs droplets, apps, kubernetes clusters, 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 DigitalOcean personal access token to pull your DigitalOcean infrastructure and billing data.

Create a token under [API → Tokens](https://cloud.digitalocean.com/account/api/tokens) with at least **Read** scope.

You'll be asked for:

-   **Personal access token**: for example `dop_v1_...`.

## 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 DigitalOcean tables are full refresh. Each sync replaces the contents of the table.

## Configuration

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

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `droplets` | Virtual machines (Droplets) running in your account. | Full refresh | — | — |
| `apps` | App Platform applications and their current specification. | Full refresh | — | — |
| `actions` | Account-wide log of actions taken on resources (creates, resizes, power cycles, transfers). | Full refresh | — | — |
| `kubernetes_clusters` | DigitalOcean Kubernetes (DOKS) clusters. | Full refresh | — | — |
| `databases` | Managed database clusters (Postgres, MySQL, Redis, MongoDB, Kafka). | Full refresh | — | — |
| `volumes` | Block storage volumes. | Full refresh | — | — |
| `snapshots` | Snapshots of Droplets and volumes. | Full refresh | — | — |
| `load_balancers` | Load balancers distributing traffic across Droplets. | Full refresh | — | — |
| `projects` | Projects used to organize resources in your account. | Full refresh | — | — |
| `vpcs` | Virtual Private Cloud networks. | Full refresh | — | — |
| `images` | User-owned images (snapshots, backups, and custom images). | Full refresh | — | — |
| `domains` | DNS domains managed by DigitalOcean. | Full refresh | — | — |
| `ssh_keys` | SSH public keys registered on the account. | Full refresh | — | — |
| `reserved_ips` | Reserved (formerly floating) IP addresses. | Full refresh | — | — |
| `tags` | Tags used to label and group resources. | Full refresh | — | — |
| `sizes` | Catalog of Droplet size plans, with the resources and price each slug maps to. | Full refresh | — | — |
| `regions` | Catalog of data center regions, resolving the region slugs carried by other resources. | Full refresh | — | — |
| `invoices` | Billing invoices for the account. | Full refresh | — | — |
| `billing_history` | Append-only ledger of billing events (invoices, payments, credits). | Full refresh | — | — |
| `invoice_items` | Line items behind each invoice, attributing spend to the resource that incurred it. | Full refresh | — | — |
| `invoice_summaries` | Per-invoice totals, split into product charges, overages, taxes, and credits. | Full refresh | — | — |
| `project_resources` | Membership table mapping each resource URN to the project it is assigned to. | Full refresh | — | — |
| `domain_records` | DNS records configured under each domain in the account. | Full refresh | — | — |
| `database_backups` | Backups available for each managed database cluster. Caching and Valkey clusters have none. | Full refresh | — | — |
| `database_events` | Event log for each managed database cluster, covering creates, updates, maintenance, and power cycles. | Full refresh | — | — |
| `app_deployments` | Deployment history of each App Platform app, with the phase each deployment reached. | Full refresh | — | — |
| `app_events` | Deployment and autoscaling events of each App Platform app. | Full refresh | — | — |
| `kubernetes_node_pools` | Node pools of each Kubernetes cluster, with their Droplet size, node count and autoscaling bounds. | Full refresh | — | — |
| `uptime_checks` | Uptime checks that monitor the availability of a URL or host. | Full refresh | — | — |
| `uptime_check_states` | Current per-region status and the most recent outage of each uptime check. | Full refresh | — | — |
| `registries` | Container registries in the account. | Full refresh | — | — |
| `registry_repositories` | Repositories in each container registry, with tag and manifest counts. | Full refresh | — | — |

## Troubleshooting

-   If the connection fails with an authorization error, the personal access 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.