DOCUMENT OPS
Publish Figma export slices to R2 with a versioned Coda manifest
When a Figma file is published, pulls every export-marked slice, uploads each to Cloudflare R2 under a content-hashed path.
How it runs
The automated pipeline, trigger to output.
- TriggerFigma file publishedFigma
- ActionRead file metadata and export-marked nodesFigma
- ActionDownload each slice as an image assetFigma
- ActionUpload slices to R2 under content-hashed keysCloudflare R2
- OutputAppend version rows to Coda manifest tableCoda
What it does
Turns a Figma "publish" event into a clean, versioned asset drop. Every node marked for export is downloaded at its configured scale, uploaded to R2 under a content-hashed key, and logged as a new row in a Coda manifest so designers and engineers always know the live CDN URL for each asset.
When to use it
Use it when your design system ships icons, illustrations, or marketing slices straight from Figma and you want a single source of truth for what is live on the CDN — without anyone hand-exporting PNGs or pasting links into a doc.
How it works
- 1A Figma publish webhook fires for the watched library file.
- 2The flow reads file metadata and collects all nodes flagged for export.
- 3It downloads each slice as an image asset at its export scale.
- 4Each asset is uploaded to R2 under a key derived from its content hash, so identical bytes dedupe and changed bytes get a fresh URL.
- 5A row per asset (name, node id, hash, CDN URL, version) is appended to the Coda manifest table for lookup.
Set it up
What you configure once, before turning it on.
- 1Connect FigmaFiles, frames, comments, assets.
- 2Connect Cloudflare R2Object storage, S3-compatible.
- 3Connect CodaDocs, packs, automations.
- 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.