> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt # Linking Harness as a source **Alpha release** This source is currently in **alpha**. The interface and available tables may change. ![](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 Harness connector syncs your CI/CD pipeline data – pipelines, executions, services, and environments – into the PostHog data warehouse, so you can analyze your deployment activity alongside your product data. ## Prerequisites You need a [Harness](https://harness.io/) account with API access. Each connection imports data from one account, organization, and project scope. To create an API key token: 1. In Harness, go to **My Profile** > **My API Keys**. 2. Create an API key and add a token. 3. Grant the token view permission for pipelines, executions, services, and environments in your project. ## 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 Harness. 3. Enter your connection details: - **API key token** – the token you created in Harness. - **Account ID** – your Harness account ID. - **Organization ID** – the organization containing your project (defaults to `default`). - **Project ID** – the Harness project to import from. - **Region** – select the host that matches your Harness account URL. Supported hosts are `app.harness.io`, `app3.harness.io`, `accounts.harness.io`, and `accounts.eu.harness.io`. Self-managed hosts aren't supported. 4. 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 Harness data in PostHog. ## Available tables | Table | Description | Sync method | | --- | --- | --- | | `pipelines` | Pipeline summaries in the selected Harness project | Full refresh | | `executions` | Pipeline executions, including status, timing, and stage counts | Full refresh | | `services` | Services configured for deployment in the selected Harness project | Full refresh | | `environments` | Deployment environments in the selected Harness project | Full refresh | **Full refresh** tables reload all data on each sync. ## Sync limitations All Harness tables use full refresh only. Execution queue-time filters could miss later status changes on older executions, so incremental sync isn't supported. ## Configuration | Option | Description | | --- | --- | | `API key token` **Type:** password **Required:** True | | | `Account ID` **Type:** text **Required:** True | | | `Organization ID` **Type:** text **Required:** True | | | `Project ID` **Type:** text **Required:** True | | | `Region` **Type:** select **Required:** True | Select the host shown in your Harness account URL. | ## Supported tables | Table | Description | Sync method | Incremental field | Primary key | | --- | --- | --- | --- | --- | | `pipelines` | Pipeline summaries in the selected Harness project. | Full refresh | — | — | | `executions` | Pipeline executions, including status, timing, and stage counts. | Full refresh | — | — | | `services` | Services configured for deployment in the selected Harness project. | Full refresh | — | — | | `environments` | Deployment environments in the selected Harness project. | Full refresh | — | — | ### Still have questions? Ask PostHog AI ### Was this page useful? HelpfulCould be better