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

# Linking CloudZero as a source

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

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

The CloudZero connector syncs your cloud cost intelligence data – costs and dimensions – into PostHog, so you can analyze cloud spend alongside your product data.

## Prerequisites

You need a [CloudZero](https://www.cloudzero.com/) account and an API key with the following scopes:

-   `billing:read_costs`
-   `billing:read_dimensions`

To create an API key, go to **Settings > API Keys** in your CloudZero dashboard.

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

-   **API key** – a CloudZero API key with the `billing:read_costs` and `billing:read_dimensions` scopes. Create one under **Settings > API Keys** in your CloudZero dashboard.
-   **Granularity** – how to bucket cost data. Options: `hourly`, `daily` (default), `weekly`, `monthly`, `yearly`.
-   **Cost type** – which cost metric to sync. Options: `billed_cost`, `discounted_cost`, `amortized_cost`, `discounted_amortized_cost`, `real_cost` (default), `on_demand_cost`, `invoiced_amortized_cost`, `usage_amount`.
-   **Group costs by dimensions** (optional) – a comma-separated list of CloudZero dimension IDs to break costs down by (e.g. `service,account`). When set, each unique combination of dimensions produces its own row. You can find available dimension IDs by syncing the **Dimensions** table.

## 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 **Costs** table supports incremental sync using the `usage_date` field. A built-in 7-day lookback window automatically re-syncs recent data on each run to capture any cost restatements CloudZero applies after the fact.

The **Dimensions** table only supports full table refresh because the CloudZero API does not expose a reliable timestamp filter for dimensions.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API key` | password | Yes |
| `Granularity` | select | Yes |
| `Cost type` | select | Yes |
| `Group costs by dimensions (optional)` | text | No |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `Budgets` | A budget defined in CloudZero: a monthly planned spend limit for a saved view, with optional alert thresholds. Sync this alongside Costs to compare planned against actual spend. | Full refresh | — | — |
| `Costs` | A time-series row of cloud/SaaS spend for a single usage period (hour/day/week/month/year), optionally broken down by one or more CostFormation dimensions (e.g. service, account). | Incremental, Full refresh | usage\_date | — |
| `Dimensions` | A CostFormation dimension available to group or filter cost data by (e.g. service, account, team). | Full refresh | — | — |
| `Insights` | A cost insight: a piece of cost work tracked in CloudZero, carrying its estimated dollar impact, effort, and status as it moves from new to addressed. | Full refresh | — | — |
| `RecommendationTypes` | A recommendation type: the pattern CloudZero evaluates to produce recommendations, such as rightsizing an over-provisioned instance. Resolves the `recommendation_type_id` on the Recommendations table. | Full refresh | — | — |
| `Recommendations` | A savings recommendation CloudZero generated for one resource, with the spend it could save over the last 30 days. CloudZero only returns recommendations at or above a $1.00 30-day cost impact by default, so lower-impact recommendations are not in this table. | Full refresh | — | — |

## Troubleshooting

### Sync failing with a 403 or "Unauthorized" error

Your API key is invalid or missing the required scopes. Verify the key in **Settings > API Keys** in your CloudZero dashboard and confirm it has the `billing:read_costs` and `billing:read_dimensions` scopes.

### Sync failing with a 410 "Gone" error

CloudZero caches paginated query results for 24 hours. If a sync takes longer than that, the cache expires and you'll see a 410 error. Retry the sync to start a fresh query.

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.