CONTENT CREATION
Nightly docs-screenshot drift scan with a single Slack digest
Every night it captures your documented screens on staging, diffs them against published docs screenshots, and posts one Slack digest listing only the screens that changed.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule
- ActionRead documented-screen list from ReadMeReadMe
- ActionCapture each screen on staging via BrowserbaseBrowserbase
- LogicDiff vs published shots, collect drifted screens
- LogicSkip run if nothing drifted
- OutputPost one Slack drift digestSlack
What it does
On a nightly schedule this template walks your list of documented UI screens, captures each one against the current staging build, compares it to the screenshot live in your docs, and sends a single Slack digest naming every screen that has drifted. No issues are created — it is a low-noise heads-up so the team decides what to recapture.
When to use it
Use it when releases are frequent or continuous and you would rather catch screenshot rot daily than wait for a release event. The one-message digest keeps it from becoming alert spam while still surfacing drift early.
How it works
- 1A nightly schedule starts the run.
- 2The flow reads the documented-screen list and their docs URLs from ReadMe.
- 3Browserbase captures each screen on the staging deployment.
- 4A diff step compares every capture to its published screenshot and collects the ones past the change threshold.
- 5A branch checks whether any screens drifted; if none did, the run ends silently.
- 6Otherwise a single Slack message lists each drifted screen with its before/after thumbnails and doc link.
Set it up
What you configure once, before turning it on.
- 1Connect ReadMeAPI docs, changelog, auth.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.