Automated Octopus Deploy Environment Tracking
Every morning, WebRun opens Octopus Deploy, checks which release version is currently live in every environment, emails the release manager when an environment is running a release older than what's already live elsewhere, and logs each environment's status to Airtable so the deployment history is easy to trace back.
How do I know if an environment is running behind in Octopus Deploy?
WebRun checks Octopus Deploy every morning for which release version is live in each environment. It emails the release manager only when an environment is running behind, and logs every environment's status to Airtable, so the deployment history is easy to trace and nothing stays stale without someone noticing.
- Behind environments get flagged the same morning, not at the next incident
- The full deployment history is traceable in one Airtable log
- The release manager gets an email only when it actually matters
Built for release managers · DevOps teams · platform engineers · software engineering teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
octopus.comin a real browser with your saved login - no setup, no API keys. -
1
Octopus Deploy - check which release is live per environment
- Open Octopus Deploy and check the currently deployed release for each environment
- Compare each environment's release against the most recent release available
- Flag any environment running a release that's clearly behind
Done when Every environment's current release version is captured and compared.
-
2
Gmail - email the release manager if any is behind
gmail.com
WebRun opens Gmail to email the release manager if any is behind. - Draft a short internal email to the release manager only when an environment is behind
- Name the environment and how far behind its release is
- Skip the email entirely when every environment is current
Done when The release manager has an email only when an environment is behind.
-
3
Airtable - log the environment status
airtable.com
WebRun opens Airtable to log the environment status. - Log each environment's current release version as a new row
- Keep prior days in place so the deployment history is traceable
- Note which environments were flagged as behind
Done when Today's release version per environment is logged in Airtable.
How is each run configured?
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.
Every action is checked against this policy before it runs.
Questions, answered
Will it deploy or promote a release itself?
No. WebRun only reports the current status. Deploying or promoting a release to an environment is always a deliberate action your release manager takes.
Do I get an email every day?
No. The email only goes out when an environment is actually behind, so a fully current deployment state stays quiet.
Can I trace back what was live on a given day?
Yes. Every day's environment status is logged as a new row in Airtable, so you can look back at what was deployed when.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.