CONTENT CREATION

Export Figma tokens to iOS, Android, and CSS files, archive them, and deploy the downloads page

Manually triggered export that converts Figma variables into platform-specific token files (Swift, XML, CSS custom properties), archives the bundle to Google Drive.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggermanual
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerOperator triggers export (optional version tag)
  • ActionFetch Figma variables; resolve modes and aliasesFigmaFigma
  • LogicTransform into Swift, Android XML, and CSS files
  • ActionZip versioned bundle and archive to Google DriveGoogle DriveGoogle Drive
  • ActionDeploy downloads page with new + prior versionsVercelVercel
  • OutputAnnounce new version with link in SlackSlack

What it does

Generates ready-to-consume token files for every platform from one Figma source. Designers and engineers on iOS, Android, and web all get the same values in their native format, plus a hosted page to download the latest bundle.

When to use it

Use it before a cross-platform release when each platform team needs tokens in their own syntax and you want a single, versioned distribution point instead of emailing files around.

How it works

  1. 1An operator triggers the export, optionally tagging a version.
  2. 2The flow fetches Figma variable collections and resolves modes and aliases into a canonical token set.
  3. 3A logic step transforms the canonical set into three outputs: Swift constants, Android XML resources, and CSS custom properties.
  4. 4The three files are zipped into a versioned bundle and uploaded to a Google Drive folder for archival.
  5. 5A Vercel deploy publishes a downloads page listing the new bundle plus prior versions.
  6. 6A Slack message announces the new version with the downloads-page link.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect FigmaFiles, frames, comments, assets.
  2. 2
    Connect Google DriveDocs, sheets, slides, 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.