DOCUMENT OPS
Sync Figma design tokens into a versioned spec PR on GitHub
When a Figma file is published, exports its design variables, diffs them against the committed token spec, and opens a GitHub pull request with the changes when they differ.
How it runs
The automated pipeline, trigger to output.
- TriggerFigma file publishedFigma
- ActionExport variable definitions from FigmaFigma
- ActionRead committed tokens.json from branchGitHub
- LogicDiff tokens; stop if unchanged
- ActionCommit new tokens + changelog to a branchGitHub
- OutputOpen pull request for reviewGitHub
What it does
Keeps your repository's design-token source of truth in lockstep with Figma. On every Figma file publish, it pulls the current variable definitions, compares them to the `tokens.json` already committed, and — only if something actually changed — opens a pull request with the new values and a human-readable changelog. No PR is opened when nothing moved.
When to use it
Use it when designers own tokens in Figma but engineering consumes them from a versioned file. It removes the manual copy-paste step and gives every token change a reviewable, revertable artifact.
How it works
- 1Figma publishes a new file version, firing the trigger.
- 2Pull the file's variable definitions (colors, spacing, type scale) from the Figma API.
- 3Read the committed `tokens.json` from the target GitHub branch.
- 4Diff the two; if they are identical, stop here.
- 5If they differ, write the new tokens and a generated changelog to a fresh branch.
- 6Open a pull request so the team reviews and merges the spec update.
Set it up
What you configure once, before turning it on.
- 1Connect FigmaFiles, frames, comments, assets.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Document Ops workflows
Batch-narrate a Google Drive PDF folder in multiple languages
On a schedule, finds PDFs in a Google Drive folder that lack audio, then generates ElevenLabs narrations in each configured language and files them into per-language subfolders…
Executed Contract Exhibit & Initials Completeness Gate
When a signed contract lands in a Dropbox intake folder, verify every required exhibit, schedule, and initialed page is present.
Flag redline deviations when a contract lands in Drive
Watches a Google Drive folder for incoming counterparty contracts, diffs each clause against your approved template library.
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
Narrate new Dropbox PDFs into MP3 audio versions
When a PDF lands in a watched Dropbox folder, extract its text and generate an ElevenLabs voice narration.
On-demand PDF narration via webhook with emailed audio link
Accepts a PDF URL through a webhook, generates an ElevenLabs narration with the requested voice, stores the MP3, and emails the requester a download link.
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.