DOCUMENT OPS
Weekly design-system health digest from the Coda catalog
Each week, reads the Coda component catalog and Figma metadata to compute coverage and freshness stats, then publishes a health digest to Confluence and Slack for stakeholders.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionRead catalog rows from CodaCoda
- ActionPull current Figma library metadataFigma
- LogicReconcile and compute coverage, freshness, orphans
- ActionPublish health digest page to ConfluenceConfluence
- OutputPost headline metrics and link to SlackSlack
What it does
Produces a weekly scorecard for the design system. It reads the Coda component catalog plus live Figma metadata and computes the numbers leadership actually asks about: total components, percentage documented, count deprecated, components changed this week, and any orphaned catalog rows whose Figma component no longer exists. The result is published as a formatted page in Confluence and summarized in Slack.
When to use it
Use it when you need a recurring, low-effort report on design-system health for design and product leadership — a trend they can watch week over week without anyone manually assembling slides.
How it works
- 1A weekly schedule starts the run.
- 2The flow reads all rows from the Coda catalog and pulls current Figma library metadata.
- 3A logic step reconciles the two: it computes documented vs undocumented coverage, deprecated counts, components modified in the last seven days, and orphaned rows.
- 4It assembles the metrics into a readable digest with the week-over-week deltas.
- 5It publishes the digest as a Confluence page under the design-system space.
- 6It posts the headline numbers and the Confluence link to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect CodaDocs, packs, automations.
- 2Connect FigmaFiles, frames, comments, assets.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 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.