CONTENT CREATION
Batch-Refresh All Doc Screenshots on a Release Tag and Log to Notion
When a release tag is pushed, recaptures the full documented screenshot set against the released build via Browserbase, regenerates stale ReadMe images.
How it runs
The automated pipeline, trigger to output.
- TriggerRelease tag pushed to GitHubGitHub
- ActionRead full documented route list from ReadMeReadMe
- ActionCapture every route against the tagged release buildBrowserbase
- LogicCompare to previous release set; select changed screens
- ActionPush changed images to ReadMe pagesReadMe
- OutputLog per-release freshness record to NotionNotion
What it does
Pins a clean screenshot refresh to every product release. The instant a version tag lands, it recaptures the entire documented UI against that exact released build, updates any ReadMe images that changed since the last release, and records an auditable freshness entry in Notion so you always know which doc images correspond to which version.
When to use it
Use it for products with discrete, tagged releases where docs must reflect the shipped version precisely, and where compliance or support needs a paper trail mapping screenshots to release numbers.
How it works
- 1A GitHub release-tag push triggers the run.
- 2The flow reads the full documented route list from ReadMe.
- 3Browserbase captures every route against the build URL for the tagged release.
- 4A logic step compares captures to the previous release's set and selects only the changed screens.
- 5The changed images are pushed to their ReadMe pages.
- 6A Notion record is created for the release listing the tag, refreshed page count, and links to the before/after images.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ReadMeAPI docs, changelog, auth.
- 3Connect BrowserbaseHeadless browsers, sessions, replays.
- 4Connect NotionPages, databases, comments.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.