CONTENT CREATION

Archive Figma hero variants to Dropbox with generated social crops

On a schedule, exports every hero frame from a Figma page, asks generate-image to produce square and wide social crops, and files all assets into a dated Dropbox campaign folder.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly schedule
  • ActionList and export hero frames from Figma pageFigmaFigma
  • LogicSkip frames unchanged since last run
  • ActionGenerate 1:1 and 16:9 social cropsImage generation
  • OutputUpload originals + crops to dated Dropbox folderDropboxDropbox

What it does

Keeps a clean, versioned asset library. It walks a designated Figma page of hero frames, exports each at full resolution, generates social-ready square (1:1) and landscape (16:9) variants, and writes everything into a dated folder in Dropbox so marketing always has the latest crops.

When to use it

Use it when heroes are reused across the blog, email, and social, and people keep re-exporting the same frame in the wrong size. A nightly archive gives one canonical source of crops per campaign.

How it works

  1. 1A nightly schedule triggers the run.
  2. 2The flow lists all frames on the configured Figma campaign page and exports each as PNG.
  3. 3For each hero, generate-image produces a 1:1 and a 16:9 variant suitable for social and headers.
  4. 4A logic step skips frames whose export hash is unchanged since the last run to avoid duplicate archiving.
  5. 5All originals and variants are uploaded into a date-stamped Dropbox folder, organized by frame name.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect FigmaFiles, frames, comments, assets.
  2. 2
    Connect Image generationManaged Nano Banana image renders, metered per image.
  3. 3
    Connect DropboxFiles and folders.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.