All templates
For open source maintainers, .NET engineering teams & platform teams

Keep an eye on your NuGet package downloads

Every morning, WebRun opens NuGet, checks the prior day's download count and latest published version for each package your team maintains, posts a summary to Slack showing the trend, and separately flags Telegram when a package's downloads spike well above its usual daily range so a sudden surge in adoption or a dependency problem gets noticed right away.

  • No credit card
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Every day at 8:00 AM WebRun
1 NuGet check the day's download counts
2 Slack post the daily digest
3 Telegram flag a big download spike
Run a sample
In short

How do I track NuGet package downloads and catch a sudden spike?

WebRun checks NuGet every morning for the prior day's download count and version of each package your team maintains, posting a summary to Slack. A package whose downloads spike well above its usual range also gets flagged separately in Telegram, so a sudden surge in adoption or a dependency problem gets noticed right away.

  • Download trends are tracked automatically every day
  • A sudden spike gets flagged instead of going unnoticed
  • The team sees package health without checking NuGet by hand

Built for open source maintainers · .NET engineering teams · platform teams · developer tooling teams

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens www.nuget.org/users/account/LogOn in a real browser with your saved login - no setup, no API keys.

  2. 1
    NuGet - check the day's download counts
    nuget.org
    WebRun in NuGet: check the day's download counts
    WebRun opens NuGet to check the day's download counts.
    • Open the NuGet page for each package your team maintains
    • Record the prior day's download count and latest published version
    • Compare the download count against the package's usual daily range

    Done when Every maintained package has yesterday's download count and version on record.

  3. 2
    Slack - post the daily digest
    slack.com How to Automate Slack
    WebRun in Slack: post the daily digest
    WebRun opens Slack to post the daily digest.
    • Post a summary of yesterday's downloads by package to the team channel
    • Show the day over day change for each
    • Note which packages are also being flagged in Telegram

    Done when The team channel has today's download summary.

  4. 3
    Telegram - flag a big download spike
    telegram.org How to Automate Telegram
    WebRun in Telegram: flag a big download spike
    WebRun opens Telegram to flag a big download spike.
    • Send a separate flag when a package's downloads spike well above its usual range
    • Name the package and the size of the spike
    • Skip this step on a day with no spike

    Done when Every package with a download spike today has a flag in Telegram.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.nuget.org/users/account/LogOn
ScheduleRuns automatically on this cadence
Every day at 8:00 AM
DeliveryHow each run's result reaches you
Download digest · Slack
OutputWhat each run produces - A daily NuGet download summary in Slack, with a Telegram flag for any package that spikes.
Digest
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it publish a new package version?

No. WebRun only reads public NuGet statistics. Publishing a new version is always done by a maintainer, on purpose.

What counts as a spike?

A download count well above the package's usual daily range, so ordinary day to day variation doesn't get flagged.

Does this work for private feeds?

It reads whatever download and version data your NuGet account has access to, including packages your team maintains on a private feed.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.