DOCUMENT OPS

Slice exportable assets from a Figma frame into a Dropbox asset library

When a frame is marked export-ready this pulls every layer flagged for export, renders each at 1x/2x/3x, and files the assets into an organized.

CategoryDocument Ops
Enginesim
Difficultybeginner
Triggerevent
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerFigma frame marked export-readyFigmaFigma
  • ActionRead node tree for export-flagged layersFigmaFigma
  • ActionRender each layer at 1x/2x/3xFigmaFigma
  • LogicNormalize file names and build manifest
  • OutputUpload assets + manifest to /assets/<frame> in DropboxDropboxDropbox

What it does

Produces the production asset set from a design frame. It finds every layer the designer marked for export, renders each one at standard pixel densities, normalizes the file names, and lands them in a tidy Dropbox folder structure so engineers grab assets without ever opening Figma.

When to use it

Use it when handoff isn't about specs but about shipping the actual icons, logos, and illustrations — and you want a consistent, density-complete asset library in Dropbox instead of one-off manual exports.

How it works

  1. 1A Figma webhook fires when a frame is marked export-ready.
  2. 2The flow reads the frame's node tree to find layers flagged for export.
  3. 3For each flagged layer it renders 1x, 2x, and 3x raster outputs.
  4. 4File names are normalized to a kebab-case convention with density suffixes.
  5. 5A manifest mapping layer names to file paths is generated.
  6. 6All assets and the manifest are uploaded into the `/assets/<frame>` library in Dropbox.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect FigmaFiles, frames, comments, assets.
  2. 2
    Connect DropboxFiles and folders.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.