DOCUMENT OPS
Nightly Figma library to Coda component catalog sync
Every night, pulls all published components from your Figma team libraries and upserts them into a Coda table so the catalog always reflects the live design system.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionList published components from Figma librariesFigma
- LogicNormalize and dedupe records by component key
- ActionUpsert each component into Coda catalog tableCoda
- OutputPost added/updated summary to SlackSlack
What it does
Keeps a Coda table in lockstep with your Figma design system. Each night it reads every published component and component set across your team libraries, captures key metadata (name, key, containing file, last-modified, description), and upserts each one into a Coda table keyed by component key. New components are added, renamed or moved ones are updated, and a `last_synced` timestamp is stamped on every row.
When to use it
Use it when your component inventory lives in a spreadsheet that goes stale the moment a designer ships a change. Good for design-system teams who want a single source of truth in Coda for docs links, owners, and adoption notes without anyone hand-copying from Figma.
How it works
- 1A nightly schedule fires the run.
- 2The flow calls Figma to list published components and component sets across the configured library files.
- 3For each component it builds a normalized record (key, name, file, node id, description, updated-at).
- 4It upserts every record into the Coda catalog table, matching on component key so edits update in place rather than duplicating.
- 5A short summary (added / updated / total) is posted to Slack so the team sees the catalog moved.
Set it up
What you configure once, before turning it on.
- 1Connect FigmaFiles, frames, comments, assets.
- 2Connect CodaDocs, packs, automations.
- 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
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.
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
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.
Draft a negotiation brief from contract clause deviations
An agent reviews a contract against approved templates, researches each deviation.
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.