CONTENT CREATION
Pixel-diff preview deploys and comment stale screenshots on the PR
When a Vercel preview deployment finishes, recapture each documented page against the preview and post a PR comment listing which screenshots differ beyond a pixel threshold.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment succeededVercel
- ActionMap manifest pages onto the preview URL
- ActionCapture each page on the previewBrowserbase
- LogicPixel-diff vs baselines; keep drifts over threshold
- OutputComment stale screenshots on the PRGitHub
What it does
After a Vercel preview deploy is ready, it screenshots every documented page on the preview URL, compares each against the committed baseline image, and comments on the pull request with the exact list of screenshots that have drifted.
When to use it
You want reviewers to know — before merge — that a change altered a screen the docs depend on, without regenerating anything automatically. A surgical heads-up beats a noisy auto-commit.
How it works
- 1Vercel's deployment-succeeded webhook fires with the preview URL and PR number.
- 2The flow loads the screenshot manifest and rewrites each capture path onto the preview domain.
- 3Browserbase captures every page at the documented viewport.
- 4A pixel-diff step compares each capture to its baseline and computes a difference ratio.
- 5A logic gate keeps only captures above the configured threshold.
- 6If any drifted, it posts a GitHub PR comment naming each stale screenshot and its diff percentage.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 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
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.