CONTENT CREATION
Recapture Doc Screenshots When a PR Touches a Documented UI Route
When a frontend PR merges, maps the changed files to documented UI routes, recaptures only those screenshots via Browserbase, and opens a follow-up PR with the updated doc images.
How it runs
The automated pipeline, trigger to output.
- TriggerPR merged to default branchGitHub
- ActionRead changed file paths from the merged PRGitHub
- LogicMap changed paths to documented routes; exit if none
- ActionRecapture affected route screenshotsBrowserbase
- OutputOpen follow-up PR with updated doc imagesGitHub
What it does
Ties screenshot freshness to your actual code changes. The moment a pull request that modifies frontend code merges to main, the flow figures out which documented screens were affected, recaptures just those images, and proposes the updated docs as its own pull request for review — no full-site re-shoot needed.
When to use it
Use it when most UI changes arrive through reviewed PRs and you want screenshots updated as part of the same change cycle, instead of waiting for a scheduled sweep to catch drift days later.
How it works
- 1A GitHub merge event on the default branch triggers the run.
- 2The flow inspects the PR's changed file paths.
- 3A logic step maps those paths to the documented routes that render them; if none match, the run exits quietly.
- 4Browserbase captures fresh screenshots for each affected route against a preview or production URL.
- 5The new images are committed to the docs repo and a follow-up pull request is opened with a diff of old versus new screenshots in the description.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Content Creation workflows
Build a Dropbox B-roll library from exported blog drafts
Triggers when a new blog draft file lands in a Dropbox folder, generates a Replicate B-roll clip for each paragraph.
Generate B-roll clips when a blog post is marked Ready in Notion
Watches a Notion blog database for posts flipped to 'Ready', splits the body into paragraphs, and generates a short B-roll video clip for each paragraph with Replicate.
On-demand: turn a blog URL into narrated B-roll clips
Accepts a blog URL via webhook, scrapes the article, generates a B-roll clip per paragraph with Replicate and a voiceover with ElevenLabs.
On-Demand Screenshot Freshness Report from a Slack Command
A writer requests a freshness check in Slack for a specific docs page; the workflow inspects every screenshot on that page, scores each by age and version gap.
Sync a Figma master frame into localized hero renders
Pulls the current master hero frame and its text layers from Figma, generates a localized image variant for each locale defined in Airtable.
Research-driven localized hero banners tuned per market
An agent researches cultural and seasonal cues for each target market, adapts the master hero concept to fit local context, generates a tailored image per locale.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.