CONTENT CREATION
Capture Doc Screenshots Across Mobile, Tablet, and Desktop Viewports
For each documented screen, captures responsive screenshots at mobile, tablet, and desktop widths via Browserbase, stores them in object storage.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled run begins for screen list
- ActionRead documented target routes from ReadMeReadMe
- ActionCapture each route at mobile, tablet, desktop widthsBrowserbase
- ActionUpload versioned image set to R2Cloudflare R2
- OutputUpdate ReadMe pages with per-breakpoint image URLsReadMe
What it does
Generates a full responsive screenshot set for your docs in one pass. Instead of a single desktop capture, it shoots each documented screen at three viewport widths, archives the versioned set to object storage, and wires ReadMe to present the appropriate image so mobile readers see mobile layouts.
When to use it
Use it when your product UI is genuinely responsive and desktop-only screenshots mislead readers on phones, or when you want a durable, versioned archive of how each screen looked at every breakpoint over time.
How it works
- 1A scheduled run begins for the documented screen list.
- 2The flow reads the target routes from ReadMe.
- 3Browserbase loads each route three times at mobile, tablet, and desktop widths and captures a screenshot per width.
- 4The captures are uploaded to an R2 bucket under a dated, versioned path.
- 5The matching ReadMe pages are updated with the new responsive image URLs for each breakpoint.
Set it up
What you configure once, before turning it on.
- 1Connect ReadMeAPI docs, changelog, auth.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect Cloudflare R2Object storage, S3-compatible.
- 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.