Automated Unleash Daily Flag Change Digest
Every morning, WebRun opens Unleash, reviews flag changes made in the last 24 hours across environments, posts a Slack digest naming each flag, its change, and who made it, and sends a Telegram alert for any production flag toggled outside business hours, since that pattern is worth a second look.
How do I keep track of every Unleash feature flag change?
WebRun reviews Unleash flag activity every morning, posting a Slack digest naming every flag changed in the last 24 hours, what changed, and who made it. Any production flag toggled outside business hours also gets a separate Telegram alert, since that pattern deserves a second look, so routine changes stay in the daily digest while unusual ones get flagged immediately.
- Every flag change is visible every morning with who made it
- Unusual after-hours production changes get flagged immediately
- The team has a running audit trail without opening Unleash directly
Built for Engineering teams · platform engineers · release managers · engineering managers
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
www.getunleash.ioin a real browser with your saved login - no setup, no API keys. -
1
Unleash - review flag changes
getunleash.io
WebRun opens Unleash to review flag changes. - Open Unleash and review flag changes made in the last 24 hours across environments
- Note which flag changed, what changed, who made it, and when
- Flag any production change made outside business hours
Done when Every flag change from the last 24 hours is recorded with who made it and when.
-
2
Slack - post the change digest
slack.com
WebRun opens Slack to post the change digest. - Post the daily digest to the engineering Slack channel
- List each flag change with the environment, the change, and who made it
- Group changes by environment
Done when The team has today's Unleash change digest in Slack.
-
3
Telegram - alert on after-hours changes
telegram.org
WebRun opens Telegram to alert on after-hours changes. - Send a Telegram alert only for a production flag change made outside business hours
- Include the flag name, the change, and who made it
- Skip this step if no after-hours production change occurred
Done when An after-hours production change alert has been sent on Telegram whenever one occurs.
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 WebRun revert a flag change it flags as unusual?
No. It only reports the change and who made it. Reverting a flag or following up with whoever made the change stays with your team.
Why does an after-hours change matter more?
A production flag change outside normal business hours is unusual enough to be worth a second look, whether it was planned or not, so it gets a separate Telegram alert instead of waiting for the next digest.
Does it cover every environment?
Yes, it reports on every environment you connect it to, so changes in staging show up in the same daily digest as production.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.