CONTENT CREATION
Broken and Missing Docs Screenshot Detector
Crawls all published doc pages, checks that every screenshot asset actually loads from the CDN, and pages the on-call docs owner when images return 404 or fail to render.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule triggers the docs crawl
- ActionCrawl docs and collect screenshot asset URLsFirecrawl
- ActionValidate each asset from the CDNCloudflare
- LogicKeep only assets that fail validation
- OutputOpen a PagerDuty incident for broken imagesPagerDuty
What it does
Guards against the most visible kind of screenshot rot: images that have gone missing entirely. It crawls every published doc page, requests each screenshot asset from the CDN, and verifies it returns a valid image rather than a 404, an error page, or a zero-byte file.
When to use it
Use it after CDN migrations, bucket renames, or large docs restructures, or simply as a standing safety net. A broken screenshot looks far worse to readers than a slightly outdated one, so missing assets warrant an immediate alert.
How it works
- 1A schedule triggers the crawl, or it can be kicked off manually after a migration.
- 2The flow crawls the published docs site and collects every screenshot asset URL.
- 3Each asset is requested from the Cloudflare-served CDN and checked for status code, content type, and non-empty body.
- 4A logic step collects only the assets that failed validation.
- 5If any are broken, the flow opens a PagerDuty incident routed to the docs on-call with the failing URLs and the pages that reference them.
Set it up
What you configure once, before turning it on.
- 1Connect FirecrawlCrawl, scrape, structured extract.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.