CONTENT CREATION
Re-Capture UI Screenshots and Queue the Ones That Visually Changed
On a Figma design publish, this agent re-captures the live UI for each tracked screenshot, pixel-diffs it against the published doc image.
How it runs
The automated pipeline, trigger to output.
- TriggerFigma design publishedFigma
- ActionCapture fresh UI screenshotsBrowserbase
- LogicPixel-diff vs published; drop unchanged
- ActionRender annotated before/after diffsImage generation
- ActionUpload captures and diffs to docs driveGoogle Drive
- OutputOpen approval thread in SlackSlack
What it does
When a design is published in Figma, this workflow drives a headless browser to retake every tracked UI screenshot, compares each fresh capture to the version currently in the docs, and queues only the images that actually shifted, attaching a side-by-side annotated diff so a writer can approve at a glance.
When to use it
Use it after design system updates when you suspect some screens changed but don't want to manually re-shoot dozens of images or regenerate ones that look identical.
How it works
- 1A Figma publish event triggers the run.
- 2An agent loads the list of tracked screenshots and their target URLs.
- 3It uses a headless browser to capture a fresh image of each screen.
- 4It pixel-diffs each fresh capture against the published doc image and discards near-identical ones.
- 5For each meaningfully changed screen it generates an annotated before/after composite highlighting the changed regions.
- 6It uploads the new captures and diffs to the docs drive and posts an approval thread in Slack.
Set it up
What you configure once, before turning it on.
- 1Connect FigmaFiles, frames, comments, assets.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect Image generationManaged Nano Banana image renders, metered per image.
- 4Connect Google DriveDocs, sheets, slides, files.
- 5Connect SlackChannels, DMs, threads, mentions.
- 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
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.