Linking NuGet 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 NuGet connector syncs packages, package versions, catalog events, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
None. The NuGet API is public, so no account or API key is needed.
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.
Track adoption of.NET libraries over time: package metadata, per-version download counts, and publish/delete events for the NuGet packages you care about.
The public NuGet V3 API allows anonymous read access, so no API key is needed. Enter the package IDs you want to track, separated by commas or new lines - e.g. Newtonsoft.Json, Serilog.
You'll be asked for:
- Package IDs: for example
Newtonsoft.Json, Serilog, Microsoft.Extensions.Logging.
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.
Some NuGet tables sync incrementally, so later runs only fetch new or updated rows. The rest are full refresh.
Configuration
| Option | Type | Required |
|---|---|---|
Package IDs | textarea | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
packages | One row per tracked package from NuGet search, including the total download count and verification status. Download totals are re-polled on every sync. Unlisted packages are hidden from NuGet search and skipped | Full refresh | — | — |
package_versions | One row per version of each tracked package from the NuGet registration index, with per-version download counts merged in from search | Full refresh | — | — |
catalog_events | Publish, edit, and delete events for the tracked packages from the append-only NuGet catalog. The first sync walks the full nuget.org catalog (tens of thousands of pages) and can take several hours; incremental syncs afterwards only read new catalog pages | Incremental, Full refresh | commit_timestamp | — |
Troubleshooting
- If the connection fails with an authorization error, the API key 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.