Linking CodeScene as a source
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.
This source is currently in alpha. The interface and available tables may change.
The CodeScene connector syncs your engineering analytics data – projects, per-file Code Health metrics, and architectural components – into PostHog, so you can correlate code quality with product usage.
Prerequisites
You need a CodeScene account (Cloud or on-prem) with API access. To generate an API token, you must have an Admin, Architect, or RestApi role in CodeScene.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- 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 CodeScene, you'll need:
- API token – generate a Personal Access Token from the CodeScene API tokens page. The token must have the Admin, Architect, or RestApi role.
- API base URL (optional) – leave blank to use CodeScene Cloud (
https://api.codescene.io/v2), or enter your on-prem CodeScene server's API URL (for examplehttps://codescene.yourcompany.com:3003/api/v2).
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_attimestamp). 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 for a full explanation of how each mode works and how to choose between them.
CodeScene tables are full refresh only, since the CodeScene API doesn't support filtering by update time. Each sync pulls the current snapshot of your projects' latest analysis data.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
API base URL | text | No |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Projects | A CodeScene project: a configured set of Git repositories analyzed together as one codebase. | Full refresh | — | — |
Files | Per-file Code Health, change frequency, defect, and cost-of-change metrics from a project's latest analysis. | Full refresh | — | — |
Components | Architectural components (logical groupings of files) and their aggregate system-health metrics from a project's latest analysis. | Full refresh | — | — |
Troubleshooting
- If your API token is invalid or has been revoked, generate a new Personal Access Token from the CodeScene API tokens page, then reconnect.
- If you receive a 403 error, verify your API token has the Admin, Architect, or RestApi role required by the API.
- For on-prem CodeScene installations, ensure the API base URL includes the full path (e.g.,
https://codescene.yourcompany.com:3003/api/v2).
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.