DOCUMENT OPS
Flag undocumented Figma components in the Coda catalog
Scans the Coda component catalog daily and flags any component whose Figma description is empty or missing a docs link.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionRead component rows from Coda catalogCoda
- ActionFetch live description and docs link from FigmaFigma
- LogicFlag components with missing or thin documentation
- ActionWrite documentation_status back to CodaCoda
- OutputPost undocumented gap list to SlackSlack
What it does
Finds the holes in your documentation. It reads the component catalog in Coda, cross-checks each row against Figma metadata, and flags components that have no description, an empty docs link, or a description shorter than a minimum length. Flagged rows get a `documentation_status` of `undocumented`, and the full gap list is delivered so an owner can close it.
When to use it
Use it when your library has grown faster than its docs and nobody knows which components are safe to use. Run it on a daily cadence so documentation debt surfaces continuously instead of in a painful audit before a big release.
How it works
- 1A daily schedule starts the run.
- 2The flow reads all rows from the Coda catalog table.
- 3For each component it fetches the live Figma description and any documentation-link field.
- 4A logic step evaluates each one: empty description, missing link, or too-short text marks it `undocumented`; otherwise `documented`.
- 5The status is written back to Coda for every row.
- 6The list of undocumented components is posted to the design-system Slack channel as an actionable checklist.
Set it up
What you configure once, before turning it on.
- 1Connect CodaDocs, packs, automations.
- 2Connect FigmaFiles, frames, comments, assets.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.