CONTENT CREATION
Flag Stale Docs Screenshots on Every UI Pull Request
On each pull request that touches UI code, captures the affected screens from a preview deployment, diffs them against the screenshots currently embedded in your docs.
How it runs
The automated pipeline, trigger to output.
- TriggerUI pull request opened or updatedGitHub
- LogicFilter to front-end changes with a preview URL
- ActionCapture affected screens on Vercel previewBrowserbase
- LogicDiff captures against published doc screenshots
- OutputComment drifted images on the PRGitHub
What it does
It watches pull requests that modify front-end code, renders the relevant screens against the PR's preview deployment, and compares those captures to the screenshots referenced in your documentation. If a screen no longer matches its published image, it posts a single PR comment listing exactly which doc pages and images are now stale.
When to use it
Use it when your product UI changes faster than your docs and reviewers keep merging changes that silently invalidate screenshots. It turns "someone will notice eventually" into a reviewer-visible checklist on the PR itself.
How it works
- 1A pull request touching UI paths opens or updates, firing a GitHub webhook.
- 2A filter step confirms the diff includes front-end files and that a Vercel preview URL is available.
- 3Browserbase loads each mapped screen on the preview deployment and captures fresh screenshots.
- 4A compare step pixel-diffs each capture against the screenshot URL recorded for that screen in the docs manifest.
- 5For screens above the drift threshold, the workflow posts a GitHub PR comment naming each affected doc page and image so the author can regenerate before merge.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect VercelDeploys, runtime logs, analytics.
- 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.