CONTENT CREATION
Auto Re-Capture Stale Screenshots and Open a PR
On a weekly schedule, captures fresh screenshots for any doc images that have drifted, commits the replacements to a branch.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionDetect drifted screenshots via live capture diffBrowserbase
- ActionUpload fresh image files to CDN bucketCloudflare
- LogicSkip if no screenshots drifted
- OutputOpen a GitHub PR swapping stale imagesGitHub
What it does
Closes the loop from detection to fix. It finds drifted doc screenshots, captures pixel-matched replacements from the live product, commits the new image files to a branch, and opens a pull request that swaps the stale images for fresh ones, leaving the merge decision to a reviewer.
When to use it
Use it when screenshot drift is frequent enough that manually re-capturing and committing images is a recurring chore. Automating the capture-and-commit step removes the tedious work while keeping human review on the actual content change.
How it works
- 1A weekly schedule starts the run.
- 2The flow identifies drifted screenshots by diffing current docs images against live captures via Browserbase.
- 3For each stale image it captures a replacement at the documented viewport and resolution.
- 4New image files are uploaded to a CDN bucket and committed to a fresh GitHub branch.
- 5A logic step skips opening a PR if nothing drifted this week.
- 6Otherwise a GitHub PR is opened with the swapped images and a summary table of what changed.
Set it up
What you configure once, before turning it on.
- 1Connect BrowserbaseHeadless browsers, sessions, replays.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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.