CONTENT CREATION

Publish a living style-guide site from Figma variables on every design-system change

When a Figma design-system file is updated, pull its variable collections, generate a static style-guide site (colors, type, spacing, components), and deploy it to Vercel.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerwebhook
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerFigma file updated (webhook)FigmaFigma
  • ActionFetch variable collections and component metadataFigmaFigma
  • LogicNormalize variables into token JSON (resolve aliases + modes)
  • ActionRender token JSON into a static style-guide siteOpenAI
  • ActionDeploy generated site to Vercel productionVercelVercel
  • OutputPost live URL and changed-token count to SlackSlack

What it does

Watches a Figma design-system file and, on every change, regenerates a public living style guide and ships it to Vercel. Designers edit variables once; the documentation site updates itself.

When to use it

Use it when your tokens live in Figma variable collections and you are tired of hand-updating a static style-guide page. Good for teams that want a single canonical URL for color ramps, type scale, spacing, and component swatches that never drifts from the source file.

How it works

  1. 1A Figma webhook fires when the design-system file is saved.
  2. 2The flow fetches all variable collections and modes (color, spacing, radius, type) plus component metadata.
  3. 3A logic step normalizes the raw variables into a token JSON (resolving aliases and light/dark modes).
  4. 4An OpenAI step renders the token JSON into a self-contained HTML/CSS style-guide page with copy-to-clipboard token names.
  5. 5A Vercel deploy step publishes the generated site to its production URL.
  6. 6A Slack message confirms the deploy with the live link and a count of tokens changed.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect FigmaFiles, frames, comments, assets.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect VercelDeploys, runtime logs, analytics.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.