CONTENT CREATION
Refresh stale ReadMe doc images in place after a release
On a release it recaptures each documented screen, uploads the new images directly to your ReadMe pages, and posts a summary of which screenshots were replaced.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub release publishedGitHub
- ActionList documented screens and ReadMe page IDsReadMe
- ActionCapture each screen via BrowserbaseBrowserbase
- LogicKeep only changed screenshots
- ActionUpload fresh images to ReadMe pagesReadMe
- OutputPost Slack refresh summarySlack
What it does
When a release ships, this template recaptures every documented UI screen, and for each one that changed it uploads the fresh image straight into the corresponding ReadMe page — replacing the stale screenshot without a code review step. It then posts a Slack summary of exactly which doc images were refreshed.
When to use it
Use it when your docs live in ReadMe and you trust automated recaptures enough to publish them directly, trading review for speed. Best for high-volume, low-risk product screenshots where staleness is worse than an occasional reshoot.
How it works
- 1A GitHub release-published event starts the run.
- 2The flow lists documented screens and their ReadMe page IDs from the ReadMe project.
- 3Browserbase captures each screen on the released build.
- 4A diff step keeps only screens whose screenshot changed.
- 5For each changed screen, the new image is uploaded to its ReadMe page, replacing the old one.
- 6A Slack summary reports the count and names of refreshed screenshots.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect ReadMeAPI docs, changelog, auth.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.