DOCUMENT OPS
Gate a Figma handoff on spec completeness before publishing to Dropbox
On a handoff request this audits the Figma frame for missing annotations, unnamed layers, and detached components.
How it runs
The automated pipeline, trigger to output.
- TriggerHandoff request webhook with frame URLHTTP webhook
- ActionFetch frame node tree and metadataFigma
- LogicRun completeness checks and branch pass/fail
- ActionOn fail: send punch list to designer in SlackSlack
- ActionOn pass: render frame export and specFigma
- OutputPublish passing packet to /ready in DropboxDropbox
What it does
Acts as a quality gate between design and engineering. It inspects a Figma frame for the things that break a handoff — unnamed layers, detached components, missing redline annotations — and only lets a frame through to Dropbox once it passes, routing failures back to the designer with a specific punch list.
When to use it
Use it when engineering keeps receiving incomplete specs and you want to enforce a consistent definition-of-ready before any packet lands in the shared Dropbox handoff folder.
How it works
- 1A designer triggers a handoff request via webhook with the frame URL.
- 2The flow pulls the frame's full node tree and metadata from Figma.
- 3It runs completeness checks: layer naming, component attachment, annotation presence.
- 4A branch decides pass or fail based on the check results.
- 5If it fails, a Slack message goes to the designer listing each missing item.
- 6If it passes, the rendered export and spec are published to the `/ready` folder in Dropbox.
Set it up
What you configure once, before turning it on.
- 1Connect FigmaFiles, frames, comments, assets.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect DropboxFiles and folders.
- 4Connect HTTP webhookTrigger any URL on agent actions.
- 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
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.