CONTENT CREATION
Flag UI-changed docs screenshots after a release and queue recaptures
After a frontend release ships, this compares the current UI against the screenshots embedded in your docs and queues recapture tasks for every screen whose UI visibly changed.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub release publishedGitHub
- ActionFetch documented-screen manifest from ReadMeReadMe
- ActionCapture each screen on the new build via BrowserbaseBrowserbase
- LogicDiff against stored shots, keep changes over threshold
- OutputOpen Linear recapture task per drifted screenLinear
What it does
When a frontend release is tagged on GitHub, this template re-renders each documented UI screen in a headless browser, diffs it against the screenshot currently embedded in your docs, and opens a Linear recapture task for every screen that drifted past a pixel threshold. Fresh screens are skipped, so reviewers only see real regressions.
When to use it
Run it on every web release when your published docs lean heavily on UI screenshots that silently rot the moment a layout, color, or label changes. It turns "someone will notice eventually" into a tracked queue the day the release lands.
How it works
- 1A GitHub release-published event fires the run with the new tag.
- 2The flow pulls the screenshot manifest (screen name to docs URL) from your ReadMe project.
- 3Browserbase loads each documented screen against the freshly deployed build and captures a current frame.
- 4A diff step scores each capture against the stored screenshot and keeps only those above the change threshold.
- 5For each drifted screen, a Linear issue is created with both images and the source doc link, tagged for the docs team.
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 LinearIssues, projects, cycles, triage.
- 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
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.