CONTENT CREATION
Audit Docs for Broken or Missing Screenshots and File GitHub Issues
Crawls all ReadMe doc pages, verifies every embedded screenshot still loads and renders.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule starts audit
- ActionEnumerate doc pages and embedded image URLsReadMe
- ActionCheck each image URL loads with a valid responseHTTP webhook
- LogicSplit images into healthy vs broken/missing
- ActionRecapture live screen as replacement for broken imagesBrowserbase
- OutputOpen a GitHub issue per broken image with replacementGitHub
What it does
Finds documentation images that have gone dead — 404s, blank renders, or removed assets — before your readers do. It scans every doc page, validates each embedded screenshot loads correctly, and for each failure files a tracked GitHub issue that includes the offending page, the broken URL, and a candidate replacement captured from the live UI.
When to use it
Use it when image assets get moved, deleted, or rot over time and you need a reliable backlog of exactly what to fix rather than discovering broken images from a customer complaint.
How it works
- 1A nightly schedule starts the audit.
- 2The flow enumerates all pages and embedded image URLs from ReadMe.
- 3Each image URL is checked over HTTP for a valid, non-empty response.
- 4A logic step splits results into healthy versus broken or missing.
- 5For each broken image, Browserbase recaptures the corresponding live screen as a suggested replacement.
- 6A GitHub issue is opened per broken image with the page link, dead URL, and replacement screenshot attached for a maintainer to apply.
Set it up
What you configure once, before turning it on.
- 1Connect ReadMeAPI docs, changelog, auth.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 3Connect BrowserbaseHeadless browsers, sessions, replays.
- 4Connect GitHubRepos, issues, pull requests, actions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.