Linking Codefresh as a source

Alpha release

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

The Codefresh connector syncs your CI/CD data – projects, pipelines, builds, images, and more – into PostHog, so you can analyze your delivery pipeline alongside your product data.

Prerequisites

You need a Codefresh account on the US SaaS host (g.codefresh.io) so you can create an API key. EU and self-hosted or on-prem installations are not yet supported.

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 Codefresh, you'll need:

API key – create one in your Codefresh user settings. Codefresh API keys are scoped per resource, so grant read access for the resources you want to sync, for example Project (projects), Pipeline (pipelines, triggers), Build (builds, images), and Step Type (step types).

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 for a full explanation of how each mode works and how to choose between them.

Codefresh tables are full refresh only.

Configuration

Option	Type	Required
`API key`	password	Yes

Supported tables

Table	Description	Sync method	Incremental field	Primary key
`projects`	A Codefresh project — a logical grouping of pipelines, with shared variables and tags.	Full refresh	—	—
`pipelines`	A Codefresh pipeline definition. The pipeline's `metadata` fields (id, name, project, …) are lifted to the row's top level; the build specification stays under `spec`.	Full refresh	—	—
`builds`	A pipeline build (workflow execution), including its status, trigger, and source commit.	Full refresh	—	—
`images`	A container image produced and tracked by Codefresh builds.	Full refresh	—	—
`triggers`	A Hermes trigger linking a trigger-event to the pipeline it fires.	Full refresh	—	—
`step_types`	A Codefresh typed step (plugin) available to pipelines, from the public and account step-type catalog.	Full refresh	—	—

Troubleshooting

If your API key is invalid or has been revoked, create a new key in your Codefresh user settings, then reconnect.
If your API key is missing the access scope needed to sync some data, grant the required resource scopes to the key in your Codefresh user settings, then reconnect.

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.