CONTENT CREATION
Detect Doc Screenshot Drift and Regenerate Stale Images in ReadMe
On a schedule, recaptures every screenshot referenced in your ReadMe docs with Browserbase, pixel-diffs them against the live product UI.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionFetch doc pages and image references from ReadMeReadMe
- ActionRecapture each documented UI route in headless browserBrowserbase
- LogicPixel-diff new vs stored; flag pages over drift threshold
- ActionUpload fresh image and update flagged ReadMe pagesReadMe
- OutputPost refresh summary to SlackSlack
What it does
Keeps the screenshots in your ReadMe documentation in sync with the actual product UI. It walks your published doc pages, re-shoots each referenced screenshot against the live app in a headless browser, compares old versus new, and swaps in fresh images only where the UI has changed — so docs never show stale buttons or renamed fields.
When to use it
Use it when your product ships UI changes faster than docs can keep up and support tickets cite outdated screenshots. Best for teams with a ReadMe-hosted developer or help center where image freshness matters but manual recapture is tedious.
How it works
- 1A weekly schedule fires the run.
- 2The flow pulls every doc page and its image references from ReadMe.
- 3Browserbase loads each documented UI route and captures a current screenshot at the same viewport.
- 4A diff step compares each new capture to the stored image and flags pages whose pixel delta exceeds a threshold.
- 5For flagged pages only, the new screenshot is uploaded and the ReadMe page body is updated to point at the refreshed asset.
- 6A run summary is posted to Slack listing which pages were refreshed and which were unchanged.
Set it up
What you configure once, before turning it on.
- 1Connect ReadMeAPI docs, changelog, auth.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.
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.
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.
Weekly: clip last week's top blog paragraph and post to socials
Runs on a weekly schedule, picks the highest-traffic paragraph from the past week's posts, generates one polished B-roll clip with Replicate.
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.
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.