CONTENT CREATION
Catch broken or missing docs screenshots on deploy and page on-call
After a docs deploy it loads every documented screen, flags screenshots that fail to render or 404, and pages the on-call engineer when a screen is outright broken.
How it runs
The automated pipeline, trigger to output.
- TriggerDocs deploy webhookHTTP webhook
- ActionRead documented-screen list from ReadMeReadMe
- ActionLoad each screen and check render via BrowserbaseBrowserbase
- LogicSplit broken renders from drifted-but-working
- OutputPage on-call via PagerDuty for broken screensPagerDuty
- OutputFile Linear recapture tasks for drifted screensLinear
What it does
This template watches for a docs deploy and then loads each documented UI screen in a headless browser to confirm the screenshot still renders — not just that it looks the same, but that it loads at all. Screens that throw, time out, or return a broken image are treated as outages and escalated to on-call, while merely-changed screens are filed as routine recapture tasks.
When to use it
Use it when a stale screenshot is annoying but a broken one is unacceptable — public docs, onboarding guides, or pages where a missing image undermines trust. It separates "recapture soon" from "fix now."
How it works
- 1A deploy webhook from your docs host fires the run.
- 2The flow reads the documented-screen list from ReadMe.
- 3Browserbase loads each screen and records render success, errors, and whether the embedded image resolves.
- 4A branch splits results: broken or missing renders versus screens that merely drifted.
- 5Broken screens trigger a PagerDuty incident for the on-call engineer.
- 6Drifted-but-working screens are filed as Linear recapture tasks.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect ReadMeAPI docs, changelog, auth.
- 3Connect BrowserbaseHeadless browsers, sessions, replays.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 5Connect LinearIssues, projects, cycles, triage.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Content Creation workflows
Full multi-format snippet pack from one episode
An agent takes a published episode and produces a complete repurposing pack: quote cards, show notes, audiogram scripts, and a thread, organized into a Notion hub page.
Guest recap email draft after episode publish
When an episode publishes, transcribe it, draft a personalized thank-you email to the guest with their best quotes and shareable links, and queue it as a Gmail draft.
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.
Audiogram script and clip-timestamp builder
From a transcript dropped in Drive, pick three viral-worthy 30-to-60-second segments, write captions and hook text, and post the clip plan to Slack for editors.
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.
Podcast episode to branded quote cards
When a new episode audio file lands in Drive, transcribe it, pull the five most quotable lines, and generate branded quote-card images ready to post.
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.