CONTENT CREATION

Re-localize image variants when the source design changes in Figma

Watches a Figma design file for updates, re-renders all locale variants from the new master.

CategoryContent Creation
Enginesim
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled poll for a new Figma master versionFigmaFigma
  • ActionExport the updated master frame from FigmaFigmaFigma
  • ActionLoad existing locales from the Notion queueNotionNotion
  • LogicRoute by whether text or only visuals changed
  • ActionRe-render each locale variant from the new masterImage generation
  • OutputWrite re-sync variants back to the Notion review queueNotionNotion

What it does

Keeps localized image assets in sync with their source design. When the master creative changes in Figma, it re-exports the new master, regenerates every existing locale variant against it, and queues them for review tagged as a re-sync so reviewers know copy may need re-checking.

When to use it

Use it when designers iterate on a master after localization has already shipped. It prevents the common failure where the English creative updates but the 15 localized versions silently fall out of date.

How it works

  1. 1A scheduled check polls the Figma file for a new published version of the master creative.
  2. 2When a change is detected, the flow exports the updated master frame from Figma.
  3. 3It loads the list of locales that already had variants from the Notion queue.
  4. 4A logic step decides whether the change touched the text layer (full re-translation) or only visuals (re-render, keep prior copy).
  5. 5generate-image re-renders each locale variant from the new master.
  6. 6Variants are written back to the Notion review queue tagged as a re-sync pass with a link to the prior approved version.

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 NotionPages, databases, comments.
  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.