CONTENT CREATION
Open a GitHub PR when Figma tokens drift from the committed Tailwind theme
On a schedule, compares Figma variable values against the tokens checked into your repo's Tailwind config and, when they diverge, opens a GitHub pull request with the regenerated…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule
- ActionFetch and flatten Figma variable mapFigma
- ActionRead committed theme file from repoGitHub
- LogicDiff Figma tokens vs committed tokens; stop if no drift
- ActionOpen PR with regenerated theme + changelogGitHub
- OutputNotify reviewer with PR link in SlackSlack
What it does
Keeps your codebase's token source (a Tailwind/CSS theme file in Git) in sync with Figma. It detects when a designer changed a value in Figma that the code has not picked up, then opens a PR so an engineer can review and merge.
When to use it
Use it when design tokens are authored in Figma but consumed in code, and you want a controlled, reviewable path for changes rather than auto-merging design edits straight to main.
How it works
- 1A daily schedule triggers the check.
- 2The flow pulls current Figma variable collections and resolves them to a flat token map.
- 3It reads the committed theme file from GitHub and parses its existing token values.
- 4A logic step diffs the two maps; if there is no drift, the run ends silently.
- 5On drift, it regenerates the theme file with the new values and a comment block listing each changed token.
- 6A GitHub step opens a pull request on a fresh branch with the updated file and a summarized changelog in the PR body.
- 7The PR link is posted to Slack for the on-duty front-end reviewer.
Set it up
What you configure once, before turning it on.
- 1Connect FigmaFiles, frames, comments, assets.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.