Localization
Localize your workflows to support multiple languages and regions.
Overview
Localize your workflows and tours to support multiple languages and regions. Internationalization (i18n) allows you to adapt your content to different languages, cultures, and regions, ensuring a better user experience for diverse audiences.
Localization features are hidden until you add a second language group to your organization. To enable localization, go to Organization settings > Localization and create a new language group.
Setup
Usage
Switching languages in the workflow editor
When editing blocks in a workflow you can switch between different languages using the language switcher below the block name in the right sidebar. To switch languages:
- Select a block in the workflow editor.
- Use the language switcher below the block name in the right sidebar.
- Choose the desired language from the dropdown menu (green dot indicates a translation exists, grey dot means a translation is missing).
- Click
Create translation
if no translation exists for the selected language. - Edit content and properties in the selected language.
Add a new translation to a block
For each block in a workflow can have translations for multiple languages. To add a translation:
- Select a block in the workflow editor.
- Switch to the language you want to add using the language switcher.
- Click on the
Create translation
button that appears after switching languages.
This will create a new translation for the block in the selected language. You can then edit the content and properties of the block in that language.
Remove a translation from a block
To remove a translation:
- Select a block in the workflow editor.
- Switch to the language you want to remove.
- Click on the trash icon next to the language name and confirm the removal.
This will remove the translation for that block in the selected language, and the block will fall back to the default language of your organization.
Supported blocks and properties
Localization is available only for Component blocks and Tour blocks. Supported block properties are string
, number
, boolean
, and select
. Unsupported blocks and properties will be the same for all language groups. You can identify unsupported blocks and properties by the globe icon next to them in the block editor.
Adding new language groups
To add a new language group:
- Go to Organization settings > Localization.
- Click on New language group.
- Name the group and add relevant languages to it.
The new language group will become available in the workflow editor, allowing you to create translations for blocks in that group. Until you add translations for the new group, it will fall back to the default language group.
Other
How do fallbacks work?
When a user enters a block, Flows will first check if the block has a translation for the users language group. If a translation exists, it will be used. If there is no matching translation, Flows will fall back to the default language group.
How to handle RTL languages?
For languages that are read from right to left (RTL), such as Arabic or Hebrew, Flows doesn't automatically apply RTL styles. You need to handle RTL languages in your custom components by applying the appropriate style changes. For example, you can use a boolean property in your custom component to indicate whether the language is RTL or not, and then apply the necessary styles based on that property.
Creating separate workflows for different languages
If needed, you can create distinct workflows for each language. This gives you full control over content and structure in each version. However, it requires more upkeep if you want to keep workflows synchronized across languages.
Last updated on