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

# Linking Argo CD as a source

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

> **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 Argo CD connector syncs your GitOps delivery data – applications, deployment history, projects, repositories, and clusters – into PostHog, so you can analyze deployment frequency, rollback rates, and other delivery metrics alongside your product data.

## Prerequisites

Argo CD is self-hosted, so your Argo CD API server must be reachable from PostHog over HTTPS with a publicly trusted TLS certificate. Servers that are only accessible on a private network or behind a VPN can't be synced.

You also need an Argo CD account with the `apiKey` capability enabled so it can generate API tokens. See the [Argo CD user management docs](https://argo-cd.readthedocs.io/en/stable/operator-manual/user-management/) for how to create a local account with `apiKey` capability.

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

-   **Argo CD server URL** – the base URL of your Argo CD API server, for example `https://argocd.example.com`.
-   **API token** – generate one with `argocd account generate-token --account <account>`. The account's [RBAC policy](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/) needs read access to the resources you want to sync, for example `applications, get`, `projects, get`, `repositories, get`, and `clusters, get`.
-   **Project** (optional) – an Argo CD project name to limit which applications are synced. Leave blank to sync all applications the token can see.

## 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.

Argo CD tables are full refresh only: the Argo CD API has no reliable way to fetch only changed records, so each sync pulls the current state. Deployment history is flattened from each application's recorded history and deduplicated across syncs.

## Configuration

| Option | Type | Required |
| --- | --- | --- |
| `Argo CD server URL` | text | Yes |
| `API token` | password | Yes |
| `Project (optional)` | text | No |

## Supported tables

| Table | Description | Sync method | Incremental field | Primary key |
| --- | --- | --- | --- | --- |
| `applications` | Argo CD applications with their sync state, health, and full desired/live specification. | Full refresh | — | — |
| `deployment_history` | One row per recorded deployment, flattened from each application's status.history. Useful for DORA metrics such as deployment frequency. | Full refresh | — | — |
| `projects` | Argo CD projects (AppProject resources), which group applications and restrict their sources and destinations. | Full refresh | — | — |
| `repositories` | Git and Helm repositories connected to Argo CD. Credential fields are never synced. | Full refresh | — | — |
| `clusters` | Kubernetes clusters Argo CD deploys to. Connection credentials are never synced. | Full refresh | — | — |
| `application_events` | Kubernetes events recorded against each Application resource, one row per event. This is the sync and health transition history behind each deployment. Argo CD stores these in Kubernetes, which expires them after about an hour, so the table only holds events seen by a sync. | Full refresh | — | — |
| `revision_metadata` | Git commit metadata for each revision an application deployed, resolved from the repository. Join it to deployment\_history on revision to get the author, message, and commit date behind a deployment. Helm chart revisions are not included. | Full refresh | — | — |
| `managed_resources` | Every Kubernetes resource an application owns, with its live and target state, so you can measure configuration drift. Argo CD masks the values inside Secret resources, but any other manifest is synced as the API returns it. | Full refresh | — | — |
| `resource_tree` | Live Kubernetes resources in each application's tree, one row per resource, with its own health status. Use it to find which resource makes an application unhealthy. | Full refresh | — | — |

## Troubleshooting

-   If your API token is invalid or expired, generate a new token with `argocd account generate-token` and reconnect.
-   If some tables come back empty, the token's RBAC policy may not grant read access to those resources. Argo CD list APIs only return the items the token is allowed to see, so grant the missing `get` permissions and re-sync.
-   If the connection fails with a certificate error, your Argo CD server is presenting a self-signed or otherwise untrusted TLS certificate. PostHog requires a publicly trusted certificate.

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.