CONTENT CREATION

Regenerate screenshots when UI routes change and open a PR

On every merge to main, detect which UI route files changed, recapture only the affected product screenshots in a headless browser.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerevent
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerPush merged to mainGitHubGitHub
  • LogicFilter diff to UI route files; exit if none
  • ActionResolve changed routes to screenshot manifest entries
  • ActionCapture fresh screenshots in headless browserBrowserbase
  • ActionCommit refreshed images to a branchGitHubGitHub
  • OutputOpen pull request with the updated screenshotsGitHubGitHub

What it does

Watches your repository for merges that touch UI route files, recaptures the product screenshots tied to those routes, and proposes the updated images back as a pull request — so your docs never drift from the live UI.

When to use it

You keep screenshots in the repo (docs-as-code) and they go stale every time a page changes. You want a tight, reviewable diff instead of a manual screenshot-and-drag ritual.

How it works

  1. 1A push to `main` fires the GitHub trigger.
  2. 2The flow diffs the commit and filters to files under your routes directory; if none changed it exits early.
  3. 3For each changed route it resolves the mapped screenshot manifest entry (route path to capture URL).
  4. 4Browserbase opens each URL at the configured viewport and captures a fresh PNG.
  5. 5The flow commits the new images to a branch and opens a pull request describing which routes triggered the refresh.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect BrowserbaseHeadless browsers, sessions, replays.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.