CONTENT CREATION
Nightly Docs Screenshot Drift Sweep
Each night, re-captures every UI screenshot referenced in your published docs, visually diffs each against the live product.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionRead docs repo and extract screenshot referencesGitHub
- ActionCapture current product screensBrowserbase
- LogicVisual-diff each capture and filter by staleness threshold
- OutputFile a Linear issue listing stale screenshotsLinear
What it does
Runs a nightly audit of every product screenshot in your documentation. For each doc image, it loads the matching live product screen, captures a fresh screenshot, and compares the two pixel regions. When the difference exceeds your threshold, the screenshot is marked stale and bundled into a single Linear issue for the docs team.
When to use it
Use it when your product UI ships faster than your docs and readers keep seeing outdated screenshots. A nightly cadence catches drift within a day instead of at the next manual docs review.
How it works
- 1A nightly schedule kicks off the sweep.
- 2The flow reads the docs repo from GitHub and extracts every screenshot reference plus the product URL each one documents.
- 3Browserbase loads each live screen and captures a current screenshot.
- 4A visual-diff step compares each fresh capture to the published image and scores the pixel delta.
- 5A logic branch keeps only screenshots whose delta crosses the staleness threshold.
- 6A single Linear issue is created listing every stale screenshot with file path, screen URL, and diff score.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.