All templates
For .NET developers, package maintainers & DevOps engineers

Renew your NuGet API keys before a publish fails

Every Monday, WebRun opens your NuGet account, reads each API key with its scopes and expiry date, records the ones expiring this month in Notion, and sends you a WhatsApp warning naming every key that needs renewing before it breaks a release.

  • No credit card
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Every Monday at 9:00 AM WebRun
1 NuGet read API keys and expiry dates
2 Notion log key scopes and renewals
3 WhatsApp warn you about expiring keys
Run a sample
In short

How do I get warned before a NuGet API key expires?

WebRun checks your NuGet API keys every Monday. It reads each key's scope and expiry date, logs the ones expiring within 30 days in Notion, and sends you a WhatsApp warning naming each key and the packages it covers, so a release never fails on publish day with a dead key.

  • Expiring publish keys are caught weeks before a release
  • Every key's scope is recorded next to its expiry date
  • Lapsed keys are named before the pipeline error is investigated

Built for .NET developers · package maintainers · DevOps engineers · open source 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 - read API keys and expiry dates
    nuget.org
    WebRun in NuGet: read API keys and expiry dates
    WebRun opens NuGet to read API keys and expiry dates.
    • Sign in to NuGet and open the API keys page on your account
    • Capture every key with its name, expiry date, and the packages or glob pattern it is scoped to
    • Note which keys expire within the next 30 days and which have already lapsed

    Done when Every API key on the account is listed with its scope and expiry date.

  3. 2
    Notion - log key scopes and renewals
    notion.so How to Automate Notion
    WebRun in Notion: log key scopes and renewals
    WebRun opens Notion to log key scopes and renewals.
    • Open your release operations database in Notion
    • Add or update a row per key with its scope, expiry date, and days remaining
    • Mark keys renewed since last week as done so the list stays short

    Done when Notion holds a current row for every NuGet key with its expiry date.

  4. 3
    WhatsApp - warn you about expiring keys
    whatsapp.com How to Automate WhatsApp
    WebRun in WhatsApp: warn you about expiring keys
    WebRun opens WhatsApp to warn you about expiring keys.
    • Send yourself a short message naming each key expiring in the next 30 days
    • Put already lapsed keys first, then the soonest expiry
    • Include each key's package scope so you know what a rotation will affect. WebRun never creates, regenerates, or deletes a key

    Done when You have this week's key renewal list on WhatsApp.

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 Monday at 9:00 AM
DeliveryHow each run's result reaches you
Key expiry list · WhatsApp
OutputWhat each run produces - A list of NuGet API keys with days left before expiry, the packages each one is scoped to, and which have already lapsed.
Text
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 regenerate or delete a NuGet key?

No. WebRun only reads the API keys page and reports what it finds. Creating, rotating, or deleting a key stays a manual step you do yourself, because a rotation breaks any pipeline still holding the old value.

How far ahead does it warn me?

Thirty days by default, and you can change that window. Keys that have already lapsed are listed first so a failing publish is explained before you start debugging the pipeline.

Does it show what each key can publish?

Yes. Every entry carries the key's scope, so you can see whether it covers one package, a glob pattern, or every package you own before you rotate it.

Put this on autopilot.

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