CONTENT CREATION
Auto-open a docs-screenshot update PR when a UI merge touches documented screens
When a PR that changes documented UI components merges, it recaptures the affected screens and opens a follow-up GitHub PR replacing the stale screenshot files in the docs repo.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub pull request mergedGitHub
- LogicMap changed files to documented screens
- LogicEnd run if no documented screen affected
- ActionRecapture affected screens via BrowserbaseBrowserbase
- OutputOpen GitHub PR swapping stale screenshotsGitHub
What it does
When a pull request merges into your frontend's main branch, this template checks whether the changed files map to any documented UI screens. For each affected screen it captures a fresh screenshot, commits the new image into the docs repo, and opens a follow-up GitHub PR that swaps the stale files for the new ones — so the screenshot fix travels right behind the code change.
When to use it
Use it when your docs screenshots live as committed image files in a repo and you want screenshot updates to be reviewable diffs rather than manual chores. It closes the loop between a UI merge and the doc image that depicts it.
How it works
- 1A GitHub pull-request-merged event fires with the changed file list.
- 2A logic step maps changed component paths to the documented screens they render.
- 3If no documented screen is affected, the run ends.
- 4Browserbase captures each affected screen on the merged build.
- 5The flow commits the new image files to a branch in the docs repo.
- 6A GitHub PR is opened with the swapped screenshots and a summary of which screens updated.
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.