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

# Linking Nebius AI as a source - Docs

Copy page

# Linking Nebius AI as a source - Docs

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

[Learn more](/wizard.md)

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

**Alpha release**

This source is currently in **alpha**. The interface and available tables may change.

The Nebius AI connector syncs metadata from your Nebius AI Studio (Token Factory) account into the PostHog data warehouse: available models, uploaded files, batch inference jobs, and fine-tuning jobs. Use it to join your inference and fine-tuning activity against product and revenue data.

## Prerequisites

You need a Nebius AI Studio (Token Factory) account and an API key with read access.

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

-   **API key** – create one in the [Nebius AI Studio console](https://studio.nebius.com/settings/api-keys) under API keys. A key with read access is enough to sync every supported 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](/docs/cdp/sources.md#sync-methods) for a full explanation of how each mode works and how to choose between them.

All Nebius AI tables sync by full refresh. The API exposes no server-side timestamp filter, so incremental sync isn't offered. The tables are small metadata catalogs, so a full refresh each run is cheap.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| API key | password | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| models | Models available to your Nebius AI Studio account for inference and fine-tuning. | Full refresh | — | — |
| files | Files uploaded to Nebius AI Studio, such as batch inputs and fine-tuning datasets. | Full refresh | — | — |
| batches | Batch inference jobs that process a file of requests asynchronously. | Full refresh | — | — |
| fine_tuning_jobs | Fine-tuning jobs that train a custom model from a base model and a training file. | Full refresh | — | — |

## Troubleshooting

-   If you get an authorization error (401), your Nebius AI API key is invalid or has expired. Create a new key in the Nebius AI Studio console, then reconnect.
-   If you get a permission error (403), your API key does not have the permissions needed to sync this data. Grant read access to the key, then reconnect.

If your sync is failing or data looks wrong, see the [Data warehouse troubleshooting guide](/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.

### Was this page useful?

HelpfulCould be better