CONTENT CREATION

Batch-render localized app screenshots from a Figma master frame

On a manual run, pulls translated UI copy from a sheet, swaps it into a Figma master frame for each target locale, exports the rendered PNGs, and files them in Dropbox by market.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggermanual
Steps7
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerOperator starts run with master frame ID + locale list
  • ActionRead translated copy table (string key x locale)AirtableAirtable
  • LogicFor each locale, map strings to Figma text nodes
  • ActionDuplicate master frame and set localized text valuesFigmaFigma
  • ActionExport each populated frame to PNGFigmaFigma
  • ActionUpload renders to per-market Dropbox foldersDropboxDropbox
  • OutputPost folder links + render counts to SlackSlack

What it does

Takes one canonical Figma screen and produces a finished screenshot for every target market, with the in-frame copy replaced by the locale's translated strings. The output is a clean set of market-labeled PNGs ready for app-store listings or landing pages.

When to use it

Run it whenever marketing finalizes a new feature screen and needs the same mockup in 8-20 languages without a designer hand-editing each one. Ideal for App Store / Play Store screenshot refreshes.

How it works

  1. 1You start the run and name the master Figma frame plus the locales to build.
  2. 2The flow reads the translated copy table from Airtable, one row per string key per locale.
  3. 3For each locale it sets the matching text-node values on a duplicate of the master frame in Figma.
  4. 4It exports each populated frame to PNG via the Figma image API.
  5. 5Renders are uploaded to Dropbox into a per-market folder (e.g. /screenshots/de-DE/).
  6. 6A Slack message posts the folder links and a per-locale render count for review.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect FigmaFiles, frames, comments, assets.
  2. 2
    Connect AirtableBases, tables, views, automations.
  3. 3
    Connect DropboxFiles and folders.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.