CONTENT CREATION
Generate component preview images for the style guide and deploy them with the site
Manually triggered build that exports each Figma component, generates clean preview/social images for them, uploads the assets.
How it runs
The automated pipeline, trigger to output.
- TriggerOperator runs the build manually
- ActionList published components and pull rendered nodesFigma
- ActionGenerate branded preview image per componentImage generation
- ActionUpload preview images to R2 and collect URLsCloudflare R2
- LogicAssemble gallery manifest (component + image + meta)
- ActionDeploy refreshed gallery site to VercelVercel
- OutputPost gallery link and new components to SlackSlack
What it does
Produces a visual component gallery for your style guide. For each published component in the Figma library it renders a polished preview image, stores it, and ships an updated gallery site so stakeholders can browse components without opening Figma.
When to use it
Use it before a design-system release or review when you want shareable, branded component thumbnails and a hosted gallery, rather than asking everyone to request Figma access.
How it works
- 1An operator triggers the run manually (e.g., ahead of a release).
- 2The flow lists published components in the Figma library and pulls each component's name, description, and rendered node.
- 3A generate-image step composes a clean, on-brand preview card for each component (consistent padding, label, background).
- 4The generated images are uploaded to R2 object storage and the public URLs are collected.
- 5A logic step assembles a gallery manifest pairing each component with its hosted image and metadata.
- 6A Vercel deploy publishes the refreshed gallery site.
- 7A Slack message links the gallery and lists newly added components.
Set it up
What you configure once, before turning it on.
- 1Connect FigmaFiles, frames, comments, assets.
- 2Connect Image generationManaged Nano Banana image renders, metered per image.
- 3Connect Cloudflare R2Object storage, S3-compatible.
- 4Connect VercelDeploys, runtime logs, analytics.
- 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
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.
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.
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.
Weekly: clip last week's top blog paragraph and post to socials
Runs on a weekly schedule, picks the highest-traffic paragraph from the past week's posts, generates one polished B-roll clip with Replicate.
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.
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.