CONTENT CREATION
Write a plain-English token changelog to Notion and refresh the style-guide changelog page
When the Figma file changes, computes which tokens were added, removed, or recolored, writes a readable changelog entry to a Notion database.
How it runs
The automated pipeline, trigger to output.
- TriggerFigma file updated (webhook)Figma
- ActionFetch current tokens; load prior snapshot from NotionNotion
- LogicCompute added / removed / modified tokens
- ActionWrite plain-English change descriptionsOpenAI
- ActionAppend dated changelog entry + store new snapshotNotion
- ActionRedeploy style guide with updated changelogVercel
- OutputPost changelog summary to SlackSlack
What it does
Turns raw Figma variable edits into a human-readable history. Each change produces a dated changelog entry describing exactly what moved (e.g., "primary-500 darkened from #3B82F6 to #2563EB"), logged in Notion and surfaced on the public style guide.
When to use it
Use it when consumers of your design system keep asking "what changed and when?" It gives product, marketing, and engineering a trustworthy audit trail of token changes without reading Figma version history.
How it works
- 1A Figma webhook fires on file save.
- 2The flow fetches the current token snapshot and loads the previous snapshot from the Notion database.
- 3A logic step computes added, removed, and modified tokens between the two snapshots.
- 4An OpenAI step writes each change as a clear one-line, plain-English description grouped by category.
- 5A Notion step appends a dated changelog entry and stores the new snapshot for next time.
- 6A Vercel deploy refreshes the style guide so its changelog section shows the latest entries.
- 7The summary is posted to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect FigmaFiles, frames, comments, assets.
- 2Connect NotionPages, databases, comments.
- 3Connect OpenAIModels, embeddings, files.
- 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
Full multi-format snippet pack from one episode
An agent takes a published episode and produces a complete repurposing pack: quote cards, show notes, audiogram scripts, and a thread, organized into a Notion hub page.
Guest recap email draft after episode publish
When an episode publishes, transcribe it, draft a personalized thank-you email to the guest with their best quotes and shareable links, and queue it as a Gmail draft.
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.
Audiogram script and clip-timestamp builder
From a transcript dropped in Drive, pick three viral-worthy 30-to-60-second segments, write captions and hook text, and post the clip plan to Slack for editors.
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.
Podcast episode to branded quote cards
When a new episode audio file lands in Drive, transcribe it, pull the five most quotable lines, and generate branded quote-card images ready to post.
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.