Unqork documentation is available in two workspaces: UnqorkAI for the latest AI-first platform, and legacy Unqork for previous versions. Use the drop-down near the logo to switch.

Translations - Workflow Builder

Prev Next

The Translations panel lets Creators add language locales and manage translated text for a workflow. When translations are enabled, end-users see labels and messages in their selected language. To open the panel, in the Workflow Builder toolbar, click Definition and select Translations.

Translations must be enabled before the Translations tab becomes active. In the Workflow Settings dialog, toggle Enable Translations in the Other section.

Toolbar

The Translations toolbar provides controls for enabling, adding, and managing locales.

Control Description
Enable Translations When checked, this setting activates translation support for the workflow. End-users see translated text in Express when a matching locale is active.
Plus Add Locale Opens a panel with a searchable language selector. Select a language, and optionally a country or region to create a region-specific variant (for example, es-MX for Mexican Spanish). Already-added locales are excluded from the list. Confirming adds a new column to the translation table.
Download Export Downloads all current translations as a CSV file.
Upload Import Uploads a CSV file to populate the translation table.
Discard Changes Reverts any unsaved changes to the translation table.
Save Translations Saves the current translation values. Saving translations does not save the workflow itself.

Translation Table

The translation table lists every translatable string in the workflow. Each row represents source string.

Column Description
English (Source) The original text key as it displays in the workflow. This column is read-only.
Locale columns One column per added locale. Each cell accepts the translated text for that string. Click Add translation... in any cell to enter text. To remove a locale, select the Trash2 delete icon in its column header.

Translations are stored globally per field. If the same field key is used in multiple workflows, the translation values are shared across all of them.


Changelog

Date Change
2026-07-09 Initial publication.