CONTENT CREATION

Scheduled app-store screenshot refresh per locale

On a schedule, pulls the latest product screenshots from Figma, regenerates localized app-store captions and frames for each storefront locale.

CategoryContent Creation
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled refresh fires
  • ActionExport current screenshot frames from FigmaFigmaFigma
  • ActionRegenerate captioned screenshots per localeImage generation
  • LogicForward only changed locales
  • ActionPost sets to Slack review channelSlack
  • OutputWrite approved-ready files to R2CloudflareCloudflare R2

What it does

Keeps localized app-store screenshots current on a recurring schedule. It pulls the latest approved frames from Figma, rebuilds the captioned store screenshots for each storefront locale, and drops the full set into Slack so the release manager can approve them before they go to the stores.

When to use it

When store listings need fresh localized screenshots every release cycle and you want a predictable cadence rather than a scramble before each submission.

How it works

  1. 1A scheduled trigger fires on the configured cadence (for example weekly).
  2. 2The flow exports the current screenshot frames from the designated Figma file.
  3. 3For each storefront locale it regenerates the framed screenshot with the localized caption banner.
  4. 4A logic step compares against the last run and only forwards locales whose source or copy changed.
  5. 5The updated localized sets are posted to a Slack review channel with the locale labels and a download link.
  6. 6Approved-ready files are also written to R2 for the submission tooling to pick up.

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 SlackChannels, DMs, threads, mentions.
  4. 4
    Connect Cloudflare R2Object storage, S3-compatible.
  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.