Automated Percy Visual Diff Review Requests
Every few minutes, WebRun checks Percy for builds with new visual differences, saves the diff snapshots to Google Drive for the record, and posts a Slack alert naming the affected pages so a designer or engineer can review and approve or reject the changes before the build merges.
How do I make sure every Percy visual diff gets a human review?
WebRun checks Percy every few minutes for builds with new visual differences, saving the diff snapshots to Google Drive and posting a Slack request asking a reviewer to approve or reject them. WebRun never approves a visual change itself, since that judgment call always belongs to a human, but it makes sure every new diff gets asked about promptly.
- Every visual diff gets a review request instead of sitting unreviewed
- A standing snapshot record exists in Drive beyond Percy's own retention
- Reviewers see exactly which pages changed without opening every build
Built for Frontend engineering teams · design system teams · QA teams · product design 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
percy.io/loginin a real browser with your saved login - no setup, no API keys. -
1
Percy - check for new visual diffs
- Open Percy and review builds with unreviewed visual differences
- Note the affected pages or components for each diff
- Check which project and branch the build belongs to
Done when Every build with unreviewed visual differences is identified with its affected pages.
-
2
Google Drive - archive the diff snapshots
drive.google.com
WebRun opens Google Drive to archive the diff snapshots. - Open the Percy Visual Diffs folder in Google Drive
- Save the diff snapshots for each unreviewed build
- Name the file with the project and build number
Done when A saved snapshot record exists in Google Drive for every unreviewed diff.
-
3
Slack - post the review request
slack.com
WebRun opens Slack to post the review request. - Post a review request to the design and engineering Slack channel
- Name the affected pages and link to the build in Percy
- Ask a human reviewer to approve or reject the changes
Done when A reviewer has been asked in Slack to approve or reject every new visual diff.
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 approve or reject the visual changes itself?
No. Approving a visual difference as expected or flagging it as a bug is always a human call. WebRun only surfaces the diff and asks a reviewer to decide in Percy.
Does this block the build from merging?
Whether an unapproved visual diff blocks a merge depends on how your Percy and CI setup is configured. WebRun's role is only to make sure a reviewer is asked, not to change your merge rules.
Why save a copy to Google Drive as well?
So there is a standing visual record outside Percy's own retention window, useful for design reviews or historical comparison later.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.