Automated Chromatic Snapshot Usage Watch
Every night, WebRun opens Chromatic, reads snapshots used so far this billing period against your plan limit, works out the burn rate and which projects are consuming most, posts the picture to Microsoft Teams, and pings Telegram when the pace would take you past the limit before the period closes.
How do I track Chromatic snapshot usage against my plan limit?
WebRun watches your Chromatic snapshot usage every night. It reads snapshots used against your plan limit for the current billing period, ranks the projects burning most, posts the burn rate to Microsoft Teams, and pings Telegram only when the pace projects past the limit before the period closes.
- Overspend is caught mid period, not on the invoice
- The noisiest project is named every night
- Telegram stays silent unless the pace projects past your plan
Built for frontend leads · design system teams · engineering managers · QA engineers
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.chromatic.com/startin a real browser with your saved login - no setup, no API keys. -
1
Chromatic - read snapshots used this period
chromatic.com
WebRun opens Chromatic to read snapshots used this period. - Open Chromatic and go to the usage view for your account
- Capture snapshots used so far in the current billing period and the plan limit
- Note the days elapsed and the days left before the period closes
- Break usage down by project and count the builds behind each project's snapshots
- Never change a plan or a project setting. WebRun only reads usage
Done when Snapshots used, plan limit, days remaining, and the per project split are captured.
-
2
Microsoft Teams - post the burn rate
microsoft.com
WebRun opens Microsoft Teams to post the burn rate. - Post tonight's usage picture to your frontend channel in Teams
- Show snapshots used, the plan limit, and the share of the period elapsed
- Project the end of period total from the current daily pace
- Rank projects by snapshots consumed so the noisiest one is obvious
Done when The team has tonight's usage, projection, and per project ranking in Teams.
-
3
Telegram - ping when the pace runs over
telegram.org
WebRun opens Telegram to ping when the pace runs over. - Send a Telegram message to the frontend lead only when the projected total goes past the plan limit
- State snapshots used, days left, and the projected overshoot
- Name the project driving the biggest share of the burn
- Stay quiet on nights when the pace is comfortably inside the plan
Done when The lead is pinged only when the period is on course to run over.
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 change my plan or turn off a project?
No. WebRun reads the usage figures in Chromatic and reports them. Upgrading a plan, pausing a project, or changing build settings stays a decision your team makes after reading the numbers.
When does it send a Telegram ping?
Only when the current daily pace projects past your plan limit before the billing period closes. On nights when usage is comfortably inside the plan, it posts to Teams and stays quiet on Telegram.
How does it work out the projection?
It takes snapshots used so far, divides by days elapsed in the billing period, and extends that daily pace across the days remaining. The figures come straight from the Chromatic usage view.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.