Languages & translation

Translate a flow so each user sees it in their own language automatically. You author the flow once in your default language, add the languages you want, and Onbixo shows each end-user the version that matches their browser - falling back to your default language when there is no translation.

How it works

Every flow has a default language - the language you wrote it in. You then add one or more target languages and translate the flow's text into them. At runtime, Onbixo reads the end-user's browser language and shows the matching translation; if none matches, they see the default language. Nothing is ever left blank - an untranslated string falls back to your original text.

Translations live inside the flow, so there is no separate site or export to manage. You review and publish them like any other change.

Setting your default language

A new workspace writes flows in English by default. You can change the workspace default in Settings → Workspace, and you can override it for one flow on the Languages tab ("Default language"). The default is the language the AI translates from and the fallback users see when their language is not available.

Adding a language

Open a flow and go to the Languages tab. Search for a language and click Add Language - this adds it to the flow, ready to translate. You can add as many languages as you need; the base language is never offered (you cannot translate a flow into the language it is already written in).

Translating - with AI or by hand

Each added language has two ways to fill it in:

• Translate with AI - translates the whole flow into that language in one click. It preserves links, formatting, and placeholders, and translates only the visible text. Re-run it any time to refresh.
• Edit - open the editor to type or adjust each string by hand, side by side with the original. Use this to fix a word, match your product's wording, or translate without AI.

The two work together: let AI do the first pass, then hand-edit anything you want to change. A row shows how many strings are translated so you can see what is left.

What gets translated

Everything an end-user reads is translatable: step titles and text, the welcome modal, checklist items, and the resource-center launcher labels and links. The standard buttons and labels - Next, Back, Done, Dismiss, the checklist headings, and so on - are translatable too, so the whole experience appears in the user's language.

Not translated: your targeting rules, URLs, and analytics - those are configuration, not user-facing copy.

Reviewing and publishing

Adding or translating a language is a draft change, exactly like editing a step. Review the translations on the Languages tab, then publish the flow to make them live. You can enable or disable each language, or remove one entirely, at any time.

Availability

Translating flows is a paid feature (Starter and above). On the free plan the Languages tab shows what is possible with an upgrade prompt. AI translation uses your monthly AI credits; typing translations by hand does not.

Notes

• Matching is by browser language - an exact match first (for example pt-BR), then the base language (pt), then your default. So one Portuguese translation can serve several regions.
• Right-to-left languages (Arabic, Hebrew) are translated correctly; the card layout itself stays left-to-right for now.
• Reordering steps never misaligns translations - each translated string is tied to its step, not its position.