CONTENT CREATION
Agent triages stale screens, recaptures, and rewrites doc captions
An agent reviews a route-change diff, decides which screenshots are genuinely affected, recaptures them, rewrites the surrounding doc captions to match the new UI.
How it runs
The automated pipeline, trigger to output.
- TriggerPush to main with changed filesGitHub
- ActionAgent judges which documented screens are affectedOpenAI
- ActionCapture fresh screenshots for affected screensBrowserbase
- ActionAgent rewrites captions and alt text to matchOpenAI
- OutputOpen a review-ready PR with images and copyGitHub
What it does
Goes beyond mechanical recapture: an agent reads the code diff and existing doc prose, judges which documented screens actually changed meaningfully, recaptures those, and updates the captions and alt text so the words match the new picture — then bundles it all into one PR.
When to use it
Your docs have descriptive captions that go wrong when the UI moves, and naive screenshot replacement leaves the text lying. You want a human-quality refresh, reviewed in one diff.
How it works
- 1A push to main triggers the agent with the changed files.
- 2The agent inspects the route diff and the current doc pages to decide which screens are materially affected.
- 3For each, Browserbase captures a fresh screenshot.
- 4The agent rewrites the affected captions and image alt text to describe the new UI accurately.
- 5It commits images and prose together.
- 6A pull request opens summarizing what changed visually and in copy, for human review.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect OpenAIModels, embeddings, files.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.