Automated Chromatic UI Change Digests
Every morning, WebRun opens Chromatic, reads yesterday's builds across your branches, records which components had visual changes and which builds failed into a Notion page, and sends the on-call engineer a Twilio text only when a build broke or changes are still unreviewed.
How do I get a daily summary of visual UI changes from Chromatic?
WebRun opens Chromatic every morning and reads yesterday's builds across your branches, capturing status, changed components, and review state. It writes a dated entry into your Notion UI changelog with links back to each build, and texts the on-call engineer through Twilio only when a build failed or changes sit unreviewed.
- Yesterday's UI changes are written down before standup, per component
- Unreviewed changes are counted daily instead of piling up unnoticed
- A broken build reaches on-call by text, not by someone noticing later
Built for frontend teams · design systems teams · QA engineers · 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.chromatic.com/startin a real browser with your saved login - no setup, no API keys. -
1
Chromatic - read yesterday's builds
chromatic.com
WebRun opens Chromatic to read yesterday's builds. - Open Chromatic and list yesterday's builds across the branches you track
- Capture each build's status, branch, commit, and who pushed it
- Note which components and stories show visual changes
- Separate changes already accepted from those still awaiting review
- Flag any build that failed outright
Done when Every build from yesterday is captured with its status and changed components.
-
2
Notion - record the UI changes
notion.so
WebRun opens Notion to record the UI changes. - Open your UI changelog database in Notion and add a dated entry
- List the components that changed, grouped by branch
- Record who pushed each build and whether the changes were accepted
- Link each entry back to its Chromatic build
- Keep a running count of unreviewed changes at the top of the page
Done when Yesterday's UI changes are written into the Notion changelog with links.
-
3
Twilio - text on-call when a build broke
twilio.com
WebRun opens Twilio to text on-call when a build broke. - Send a short text to the on-call number on your own team list
- Text only when a build failed or unreviewed changes are over your limit
- Name the branch, the component count, and the person who pushed
- Never text anyone outside your team list, and never a customer
- Stay silent when every build passed and nothing is waiting
Done when On-call has been texted about broken or unreviewed builds, or nothing was sent.
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 accept or deny visual changes in Chromatic?
No. WebRun reads build status and change lists only. It never accepts a snapshot, denies a change, or approves a build. Review stays a human decision every time.
Who can it text?
Only the on-call numbers on the team list you give it, and only when a build failed or unreviewed changes exceed your limit. It never texts a customer, and any number outside your list is left for a human.
Does it write to Notion every day?
Yes. The changelog entry is written even on quiet days so the history is unbroken. The Twilio text is the part that stays silent when everything passed.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.