cio-localization

Extract every localized banner image out of a Customer.io campaign and upload labelled copies into Assets, sorted into per-language folders. Use this whenever the person wants to "витягнути банери" from a campaign, asks where a campaign's translated images live, wants banners organised by language or by email step, is migrating a currency-split campaign into Design Studio nodes, or needs a picture reference of which banner belongs to which email and locale. Also use it before building any per-locale email in Design Studio, since the banners have to exist somewhere findable first, and use it as the banner half of cio-campaign-to-design-studio, which delegates that work here rather than repeating it. Do NOT walk the campaign graph by hand or guess which currency branch to follow — read this skill first, it documents the traps that produced wrong data twice.

Put the correct localized images into every language version of a Customer.io Design Studio email (any workspace, any campaign), once the person tells you which email(s) and which Assets folder holds the banners. Use this whenever the person says "постав правильні банери", "банери по локалях", "картинки не перекладені", asks why a translated email still shows English images, hands over a Design Studio node that n8n has just translated, points at an Assets folder of per-language images, or asks which banner belongs to which locale. Do NOT reconstruct the email HTML by hand, paste bodies into context, or verify by eye — read this skill first, it documents the file-based write pipeline that turns a three-hour job into a two-minute one, and the checks that actually catch a wrong swap.

Audit and fix a Customer.io in-app message so a money amount comes from a Liquid currency snippet instead of a hardcoded figure, across every language version of that step. Use this skill whenever the person pastes a Customer.io in-app action link (…/journeys/automations/{campaign}/setup/workflow/actions?actionId=…) and asks to "check if the snippet is everywhere", "collect all the languages into one", "put the snippet in", "replace the currency split", or asks which locales/currencies an in-app covers. Also use it before any bulk migration away from per-currency branching. Do NOT edit in-app templates by hand-guessing the PUT payload — read this skill first, it documents which fields must be written together or the change silently reverts.