CONTENT CREATION
Sweep docs for broken or missing screenshot links and triage
Checks every image reference in your knowledge base for broken or 404 links, recaptures the missing screen where the source page is known.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule launches the broken-link sweep
- ActionExtract all image URLs and source articles from ReadMeReadMe
- LogicHTTP-check each URL; isolate broken linksHTTP webhook
- LogicBranch: recoverable source page vs needs-human
- ActionRecapture recoverable screens and repair the ReadMe imageBrowserbase
- OutputOpen Linear triage issue for unrecoverable linksLinear
What it does
Crawls all image references across your ReadMe docs and verifies each one resolves. For broken links where the workflow can identify the live source page, it recaptures a fresh screenshot and patches the doc. For broken links it can't auto-resolve, it files a triage ticket so nothing rots silently.
When to use it
Run it whenever migrated CMS content, expired CDN links, or deleted assets leave docs full of broken-image icons. It separates the auto-fixable from the genuinely-needs-a-human cases.
How it works
- 1A daily schedule launches the sweep.
- 2ReadMe action extracts every image URL and its containing article.
- 3An HTTP check logic step tests each URL and isolates the broken ones.
- 4A branch decides: known source page recapture, unknown to ticket.
- 5Browserbase recaptures recoverable screens and the doc image is repaired in ReadMe.
- 6Unrecoverable broken links open a triage issue in Linear for an editor.
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 LinearIssues, projects, cycles, triage.
- 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.