NuGet
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.
Connect NuGet to PostHog to sync your data into the PostHog data warehouse for analysis and modeling.
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.
Configuration
| Option | Type | Required |
|---|---|---|
Package IDs | textarea | Yes |
Linking NuGet to PostHog
- Go to the Data pipeline page in PostHog
- Click New source and select NuGet
- Fill in the required configuration fields
- Click Next, select the tables you want to sync, and then press Import
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 | — |