CONTENT CREATION

Caption new Dropbox hero exports and log them in Coda

Watches a Dropbox folder for newly dropped Figma hero exports, generates a caption and alt text for each, and records the file, caption, and a CDN-ready link in a Coda asset…

CategoryContent Creation
Enginesim
Difficultybeginner
Triggerevent
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew file in Dropbox Hero InboxDropboxDropbox
  • LogicFilter to image files only
  • ActionGenerate caption + alt textImage generation
  • ActionCreate Dropbox shared linkDropboxDropbox
  • OutputLog file, caption, and link in Coda trackerCodaCoda

What it does

Closes the loop for teams that already export heroes to Dropbox by hand. It watches an inbox folder, and for every new image generates a caption and accessibility alt text, then logs the file name, caption, and shareable link as a row in a Coda asset tracker so nothing goes uncatalogued.

When to use it

Use it when designers export heroes to a shared Dropbox folder rather than triggering off Figma directly, and you need a searchable index of every hero with its caption ready for reuse.

How it works

  1. 1A new image file lands in the watched Dropbox "Hero Inbox" folder (trigger).
  2. 2A logic step filters to image files only, ignoring non-image drops.
  3. 3generate-image produces a caption and alt text from the new hero.
  4. 4The flow creates a Dropbox shared link for the file.
  5. 5A row is added to the Coda asset tracker with file name, caption, alt text, and the shareable link.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DropboxFiles and folders.
  2. 2
    Connect Image generationManaged Nano Banana image renders, metered per image.
  3. 3
    Connect CodaDocs, packs, automations.
  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.