DOCUMENT OPS
Alert on deprecated components still in use across Figma files
When a component is marked deprecated in the Coda catalog, finds every Figma file still using it and opens a GitHub issue with the migration list so the deprecation actually lands.
How it runs
The automated pipeline, trigger to output.
- TriggerCoda row marked deprecatedCoda
- ActionSearch Figma files for instances of the componentFigma
- LogicCompile usage list; skip if no instances remain
- ActionOpen GitHub migration tracking issueGitHub
- OutputPost issue link to Slack and stamp Coda rowSlack
What it does
Turns a deprecation flag into action. When an operator marks a component `deprecated` in the Coda catalog, the flow searches your Figma files for live instances of that component, builds a list of files and frames still using it, and opens a tracking GitHub issue so the cleanup is owned and visible.
When to use it
Use it when deprecating a component is a decision but never a finished task — the old variant lingers in product mocks for months. This closes the loop by naming exactly where the deprecated component still lives and assigning the migration as real work.
How it works
- 1A Coda row update where `lifecycle` changes to `deprecated` triggers the flow.
- 2The flow reads the deprecated component's key from the changed row.
- 3It queries Figma for files and nodes that still instance that component.
- 4A logic step compiles the usage list and skips firing if there are zero remaining instances.
- 5It opens a GitHub issue titled with the component name, listing every file and a link to migrate.
- 6It posts the issue link to Slack and stamps the Coda row with the open issue URL.
Set it up
What you configure once, before turning it on.
- 1Connect CodaDocs, packs, automations.
- 2Connect FigmaFiles, frames, comments, assets.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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
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.