Skip to content

Translating a Workflow

Take an English workflow and produce the Spanish version (or vice versa). The dialogue gets translated; everything else — image prompts, video prompts, structure — stays.

This is Script Writer Mode 2 under the hood, packaged as a variant.

When you'd do this

  • A winning English workflow needs a Spanish counterpart
  • A Spanish workflow is being expanded to English-language accounts
  • Localizing for a regional Spanish dialect (Mexican Spanish vs. Castilian, etc.)

What you do

You: translate XYZS1-V1 (currently English) into Spanish. Keep everything
     visually identical — same scenes, same wardrobe, same camera.

Claude:
  Translation pass starting. Script Writer Mode 2.

  Target: Spanish, Mexican dialect (matches existing ES accounts).
  Preserving: tone (warm conversational), structure (hook / body / CTA),
              compliance constraints, scene count.
  Translating: all dialogue text in the Dynamic Prompt nodes.
  Leaving alone: image prompts, video prompts, references, schema.

  Translation complete. Sample line:

  Before (EN): "If you're a woman over 40 and your sleep stopped
                working when you hit 45 — this might be the missing
                piece."

  After (ES): "Si eres una mujer mayor de 40 y tu sueño dejó de
               funcionar cuando llegaste a los 45, esta podría ser
               la pieza que falta."

  Saving as XYZS1-V1-1.nbflow in approved/ (translations are auto-approved
  like other Lvl 1 variants).

  Ready to generate.

What changes

Only dialogue text changes. Everything else stays:

Element Translated?
Dialogue rows in Dynamic Prompts YES
Image prompts NO (visual description doesn't translate)
Video prompts NO (motion direction doesn't translate)
Universal Veo template NO
Avatar reference images NO
Setting / environment NO
Scene structure NO
Compliance constraints NO (translate per-language compliance rules separately if needed)

CTA mechanic differences per language

The CTA usually translates straightforwardly, but the sales channel mechanics may differ:

  • TikTok Shop — Shop button works the same globally
  • Amazon (via keyword) — the comment keyword needs to make sense in the target language. "GLOW" might become "BRILLO" in Spanish, or stay "GLOW" if your audience is bilingual
  • Meta Shop — same as TikTok Shop globally
  • AI Label Trick — TikTok-only requirement, applies globally

If the keyword changes, also update the ManyChat automation for that account — the trigger word needs to match.

Dialect & regional variation

Spanish has meaningful regional variation. Specify the target:

  • Mexican Spanish — most common North American Hispanic market
  • Castilian Spanish — Spain
  • Argentinian Spanish — Argentina-specific phrasing (vos instead of tú)
  • Neutral Latin American — broad reach, slight rigidity

The Script Writer defaults to Mexican Spanish for ES accounts unless told otherwise.

You: translate to Castilian Spanish, not Mexican — the account is targeting
     viewers in Spain.

Claude: [Mode 2 with Castilian flag — uses "vosotros", second-person plural,
         Castilian vocabulary]

What the translation doesn't catch

  • Cultural references that don't transfer (US-specific food, brands, idioms)
  • Compliance words in the target language that aren't in the source's banned list
  • Length differences — Spanish is typically 10-20% longer than English; the same script may exceed an 8-second Veo clip in the target language

For the third one, the Script Writer trims where possible, but if a scene's clip would overflow, you'll be told and can decide: shorten the line, split the scene, or accept the overflow and trim in post.

Version naming

Translations are decimal-bumps like other Lvl 1 / 2 variants:

V1   → V1-1     translation
V1-1 → V1-2     another translation, or any Lvl 1/2 variant

The version history note records what was translated (e.g., "EN → ES Mexican").

Multi-language workflows

If your account portfolio includes both EN and ES accounts, you might end up with:

XYZS1-V1.nbflow             original (EN tabs only)
XYZS1-V1-1.nbflow           ES translation (ES tabs)

Or both languages in one file with multiple tabs (one tab per account, mixed EN/ES). Either is valid. The single-file approach is simpler but the per-language file makes the dialect easier to manage.

When you're ready

→ Next: Adapting an Existing Script — take a script that already exists (someone else's, or one of your old ones) and produce a workflow from it. Script Writer Mode 1.