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

# Linking Aiven as a source

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

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

- [Adding a data source](#adding-a-data-source)
- [Available tables](#available-tables)
- [Sync limitations](#sync-limitations)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)

**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 Aiven connector syncs your projects, services, and billing data from [Aiven](https://aiven.io) into the PostHog data warehouse.

## Adding a data source

1.  Go to the [sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section in PostHog.
2.  Click **\+ New source** and then click **Link** next to Aiven.
3.  You need an API token from Aiven. Go to your [Aiven profile authentication page](https://console.aiven.io/profile/auth) and create a personal token. If you want to sync billing tables (billing groups, invoices, invoice lines) or organization membership tables, your token needs organization-level read access.
4.  Back in PostHog, enter the token in the `API token` field and click **Next**.
5.  Select the tables you want to sync, set the sync frequency, then click **Import**.

Once the syncs are complete, you can start using Aiven data in PostHog.

## Available tables

| Table | Description | Sync method |
| --- | --- | --- |
| `projects` | Aiven projects — the container that groups services and their billing | Full refresh |
| `organizations` | Aiven organizations — the top-level tenant that owns projects and billing | Full refresh |
| `services` | Running Aiven managed services (Kafka, PostgreSQL, ClickHouse, OpenSearch, etc.) | Full refresh |
| `billing_groups` | Billing groups that aggregate charges for one or more projects | Full refresh |
| `invoices` | Issued invoices for a billing group | Full refresh |
| `invoice_lines` | Per-service cost breakdown on invoices, used for BI cost export | Full refresh |
| `organization_users` | Members of an Aiven organization | Full refresh |
| `user_groups` | User groups within an organization for grouping members and permissions | Full refresh |
| `clouds` | Global catalogue of Aiven cloud regions across AWS, GCP, and Azure (off by default) | Full refresh |

**Full refresh** tables reload all data on each sync.

## Sync limitations

All tables use **full refresh** only. The Aiven API does not support pagination or server-side timestamp filters, so incremental syncing is not available.

## Configuration

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

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `projects` | An Aiven project — the container that groups services and their billing. | Full refresh | — | — |
| `organizations` | An Aiven organization — the top-level tenant that owns projects and billing. | Full refresh | — | — |
| `services` | A running Aiven managed service (Kafka, PostgreSQL, ClickHouse, OpenSearch, etc.). | Full refresh | — | — |
| `project_users` | A member of an Aiven project and the access they hold on it. | Full refresh | — | — |
| `project_events` | An entry in a project's audit and state-change event log. | Full refresh | — | — |
| `billing_groups` | A billing group that aggregates charges for one or more projects. | Full refresh | — | — |
| `invoices` | An issued invoice for a billing group. | Full refresh | — | — |
| `organization_users` | A member of an Aiven organization. | Full refresh | — | — |
| `user_groups` | A user group within an organization for grouping members and permissions. | Full refresh | — | — |
| `user_group_members` | Membership rows linking users to an organization's user groups. | Full refresh | — | — |
| `billing_group_projects` | Mapping of projects to the billing group they are billed under. | Full refresh | — | — |
| `invoice_lines` | A single cost line on an invoice — the per-service breakdown used for BI cost export. | Full refresh | — | — |
| `clouds` | Global catalogue of Aiven cloud regions across AWS, GCP and Azure. | Full refresh | — | — |