Linking JFrog (Artifactory / JFrog Platform) 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.

Learn more

Alpha release

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

The JFrog (Artifactory / JFrog Platform) connector syncs repositories, artifacts, builds, 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

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.

Connect your JFrog Platform instance to pull your Artifactory data.

Enter your platform URL (e.g. https://mycompany.jfrog.io, or your own domain for self-hosted installs) and an access token. Generate a token from your JFrog user profile (Edit Profile → Generate an Identity Token) or, as an admin, under Administration → User Management → Access Tokens.

The artifacts and repositories tables work with any authenticated token that can read your repositories. The builds and storage_summary tables require an admin user (or a token scoped to those APIs); deselect them if your token can't access them.

You'll be asked for:

Platform URL: for example https://mycompany.jfrog.io.
Access token

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.

Some JFrog (Artifactory / JFrog Platform) tables sync incrementally, so later runs only fetch new or updated rows. The rest are full refresh.

Configuration

Option	Type	Required
`Platform URL`	text	Yes
`Access token`	password	Yes

Supported tables

Table	Description	Sync method	Incremental field	Primary key
`repositories`	A repository configured in Artifactory — local, remote, virtual, or federated — that stores or proxies packages.	Full refresh	—	key
`artifacts`	A file (artifact) stored in an Artifactory repository, with its coordinates, checksums, and timestamps. Queried via AQL over the items domain.	Incremental, Full refresh	modified, created	repo, path, name
`builds`	Requires an admin user or a token scoped to the builds domain	Incremental, Full refresh	created	name, number
`artifact_statistics`	Download counts for artifacts that have been downloaded at least once	Full refresh	—	repo, path, name
`build_artifacts`	Requires an admin user or a token scoped to the builds domain	Incremental, Full refresh	build_created	build_name, build_number, module_name, name
`build_dependencies`	Requires an admin user or a token scoped to the builds domain	Incremental, Full refresh	build_created	build_name, build_number, module_name, name
`build_promotions`	Requires an admin user or a token scoped to the builds domain	Full refresh	—	build_name, build_number, created, status
`xray_violations`	Requires JFrog Xray and a token with Xray Read permission	Incremental, Full refresh	created	violation_details_url
`storage_summary`	Point-in-time snapshot of per-repository storage usage. Requires an admin token	Full refresh	—	repoKey

Troubleshooting

If the connection fails with an authorization error, the access token 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. If that doesn't help, contact support – we're happy to help.