DOCUMENT OPS
Upload only changed Figma slices by diffing hashes against the Coda manifest
On a schedule, re-exports every Figma slice, compares each content hash to the last recorded version in Coda, and uploads to R2 only the assets that actually changed.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule
- ActionExport and hash all Figma slicesFigma
- ActionLook up latest hash per asset in CodaCoda
- LogicBranch: skip unchanged, keep changed/new
- ActionUpload changed slices to R2Cloudflare R2
- OutputWrite new version rows to Coda manifestCoda
What it does
Keeps your CDN in sync with Figma without re-uploading everything. On each run it exports the current slices, computes a content hash per asset, and checks it against the version already logged in the Coda manifest. Only genuinely changed assets are pushed to R2 and recorded as a new version.
When to use it
Use it for large icon or illustration sets where a full re-export wastes bandwidth and clutters version history. It is ideal when most assets are stable between releases and you only want CDN churn for the handful that designers actually touched.
How it works
- 1A daily schedule kicks off the sync.
- 2The flow exports every export-marked slice from the Figma file and hashes each one.
- 3For each asset it looks up the latest hash stored in the Coda manifest.
- 4A logic step splits assets into unchanged (skip) and changed/new (upload).
- 5Changed assets are uploaded to R2 under a fresh content-hashed key.
- 6New version rows are written back to the Coda manifest, leaving unchanged assets untouched.
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
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.
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.
Triage emailed contract redlines and route by risk
When a counterparty emails a redlined contract, extracts the attachment, diffs clauses against approved templates.
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.
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.