DOCUMENT OPS
File Linear tickets when code-used tokens fall out of the Figma spec
On a schedule, an agent exports the Figma token spec, scans the codebase for token references.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled token audit
- ActionExport valid token names from FigmaFigma
- ActionScan codebase for token referencesGitHub
- LogicReconcile usage; isolate orphaned tokens
- ActionOpen Linear ticket per mismatchLinear
- OutputPost audit summary to SlackSlack
What it does
Finds the gap between the tokens designers maintain in Figma and the tokens engineers actually reference in code. An agent pulls the current Figma spec, scans the repository for token usage, and for every reference that no longer matches a valid Figma token, it files a Linear ticket describing the orphaned token and where it is used.
When to use it
Use it when design and code token sets drift apart over time and you want a standing audit that turns each mismatch into trackable engineering work instead of a silent inconsistency.
How it works
- 1The schedule starts the audit.
- 2Export the current valid token names from the Figma file.
- 3Scan the GitHub repository for design-token references in code.
- 4The agent reconciles usage against the spec and isolates orphaned or renamed tokens.
- 5For each mismatch, open a Linear ticket with the token name and file locations.
- 6Post a one-line audit summary to Slack with the count of tickets filed.
Set it up
What you configure once, before turning it on.
- 1Connect FigmaFiles, frames, comments, assets.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.