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

# Linking Cloudsmith as a source

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

> **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 Cloudsmith connector syncs repositories, packages, entitlements, 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.

Sync your Cloudsmith repositories, packages, entitlements, webhooks, vulnerability scans, audit log, members and teams.

Create an API key in Cloudsmith under **Account settings → API settings**. The key inherits your own access, so use a key from a user who can see every repository you want to sync. The workspace is the slug in your Cloudsmith URLs, for example `acme` in `https://cloudsmith.io/~acme/`.

You'll be asked for:

-   **API key**
-   **Workspace**: for example `acme`.

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

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `API key` | password | Yes |
| `Workspace` | text | Yes |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `repositories` | A repository in the workspace: the container that packages are pushed to and installed from. | Full refresh | — | — |
| `packages` | A package (artifact) stored in a repository, with its version, size, download count and synchronisation status. | Incremental, Full refresh | uploaded\_at | — |
| `entitlements` | An entitlement token for a repository: a download credential with its own usage limits and counters. The token value itself is never synced. | Full refresh | — | — |
| `webhooks` | A webhook configured on a repository, including the events it fires on and the delivery health of its most recent request. The destination URL and request-body templates are not synced, since either can embed a delivery credential. | Full refresh | — | — |
| `vulnerabilities` | The result of a vulnerability scan of a package in the workspace, with the number of findings and the highest severity found. | Full refresh | — | — |
| `audit_log` | An audit log entry for the workspace: who did what, to which object, and when. Availability depends on your Cloudsmith plan. | Full refresh | — | — |
| `repository_audit_log` | An audit log entry for a single repository: who did what, to which object, and when. Availability depends on your Cloudsmith plan. | Full refresh | — | — |
| `package_dependencies` | A dependency declared by a package, including transitive dependencies where the package format supports them. | Full refresh | — | — |
| `quota_history` | Bandwidth and storage usage for the workspace over each quota period, measured against the plan limits. | Full refresh | — | — |
| `members` | A member of the Cloudsmith organization, with their role, team memberships and login activity. | Full refresh | — | — |
| `teams` | A team within the Cloudsmith organization. Teams group members so repository privileges can be granted in bulk. | Full refresh | — | — |

## Troubleshooting

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