CONTENT CREATION

Localized launch kit from a Figma screenshot set

On a Figma export trigger, builds a full per-locale launch kit — hero image, social card, and email header.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggermanual
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerLaunch owner submits Figma frames + markets
  • ActionExport screenshot frames from FigmaFigmaFigma
  • ActionGenerate hero, social, and email assets per marketImage generation
  • LogicVerify complete asset set per market
  • OutputFile assets into Google Drive by marketGoogle DriveGoogle Drive

What it does

Produces a complete localized launch kit from a set of approved Figma product screenshots. For each target market it generates the three assets a launch needs — a hero image, a social share card, and an email header — and organizes them in Google Drive by market.

When to use it

When a product launch needs ready-to-use marketing assets across several markets and you want one run to produce the entire localized package instead of briefing design per region.

How it works

  1. 1The flow is triggered with a Figma file key, the source frame IDs, and the launch's target markets.
  2. 2It exports each referenced screenshot frame from Figma.
  3. 3For every market it generates the three asset formats with localized headlines sized for hero, social, and email placements.
  4. 4A logic step confirms each market has a complete three-asset set and lists any gaps.
  5. 5The assets are uploaded into a `Launch/<market>/` folder structure in Google Drive.
  6. 6A summary of folder links per market is returned for the launch owner.

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 Google DriveDocs, sheets, slides, files.
  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.