DOCUMENT OPS
Intake review for newly published Figma components
When a new component is published to a Figma library, drafts a catalog entry in Coda, asks an LLM to propose a description and category.
How it runs
The automated pipeline, trigger to output.
- TriggerNew component published to Figma libraryFigma
- ActionFetch component name, note, and screenshotFigma
- ActionDraft description and category with LLMOpenAI
- ActionCreate pending_review draft row in CodaCoda
- OutputRoute draft to Slack for one-click approvalSlack
What it does
Gives every new component a clean front door into the catalog. The moment a component is published to a watched Figma library, the flow creates a draft row in Coda, uses an LLM to propose a plain-English description, suggested category, and naming-convention check, then sends the draft to Slack for an owner to approve or edit before it goes live in the catalog.
When to use it
Use it when components land in the library with cryptic names and no description, and you want a consistent intake step instead of retroactive cleanup. Best for teams that want human review on every addition but don't want to write the first draft from scratch.
How it works
- 1A Figma webhook fires when a new component is published to a watched library file.
- 2The flow pulls the new component's name, screenshot reference, and any author note.
- 3An LLM step drafts a description, proposes a category, and flags naming-convention violations.
- 4A draft row with status `pending_review` is created in Coda.
- 5The draft is posted to Slack with Accept and Edit actions for the owner.
- 6On accept, the Coda row flips to `published`.
Set it up
What you configure once, before turning it on.
- 1Connect FigmaFiles, frames, comments, assets.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect CodaDocs, packs, automations.
- 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
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.
Gate contract signing on clause-deviation approval
When a contract is submitted for signature via webhook, diffs its clauses against approved templates and either auto-approves clean documents or holds them in Slack for explicit…
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
Draft a negotiation brief from contract clause deviations
An agent reviews a contract against approved templates, researches each deviation.
Log contract clause deviations to a Notion review register
On a daily schedule, scans a Drive contracts folder, diffs clauses against approved templates with OpenAI.
Weekly audit of clause drift across the contract repository
Each week, scans all executed contracts in Drive, measures how far each clause has drifted from approved templates.
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.