Actions5
- Translation Actions
- Import Actions
- Export Actions
Overview
This node integrates with the Tolgee API to export translation data from a specified project. It is useful for developers and localization teams who want to programmatically retrieve translations in various formats for use in applications or further processing.
Typical scenarios include:
- Exporting translations for mobile apps (Android, iOS/Apple, Flutter).
- Retrieving JSON or other format files for web or backend services.
- Filtering exported keys based on translation state, tags, namespaces, or presence of screenshots.
- Exporting multiple languages at once, optionally as a ZIP archive containing separate files per language.
For example, you might export all translated strings in JSON format for your Android app, filtering out untranslated keys and only including keys with screenshots.
Properties
| Name | Meaning |
|---|---|
| Project Name or ID | The ID of the Tolgee project to export from. You can select from a list of projects or specify an ID via expression. |
| Language Names or IDs | One or more language tags to export. Selecting one language returns a single JSON file; selecting multiple languages returns a ZIP file with separate JSON files per language. |
| Format | The export file format. Options include: ANDROID, APPLE, FLUTTER, JSON, PO, PROPERTIES, XLIFF, YAML, YAML_FLAT, YAML_NESTED. |
| Options | Additional export options as a collection of filters and settings: |
| - Filter Auto Translated In Language | Comma-separated list of languages to filter out auto-translated keys. |
| - Filter Has No Screenshot | Boolean to filter keys that have no screenshots. |
| - Filter Has Screenshot | Boolean to filter keys that have screenshots. |
| - Filter Key ID | Comma-separated key IDs to filter by. |
| - Filter Key Name | Comma-separated key names to filter by. |
| - Filter Key Prefix | Filter keys by prefix string. |
| - Filter Key Suffix | Filter keys by suffix string. |
| - Filter Namespace | Comma-separated namespaces to filter by. |
| - Filter No Namespace | Comma-separated namespaces to exclude keys without these namespaces. |
| - Filter No Tag | Comma-separated tags to exclude keys without these tags. |
| - Filter Not Outdated Language | Comma-separated languages to filter keys with non-outdated translations. |
| - Filter Outdated Language | Comma-separated languages to filter keys with outdated translations. |
| - Filter State | Filter by translation state in format languageTag,state (e.g., en,TRANSLATED). |
| - Filter Tag | Comma-separated tags to filter by. |
| - Filter Translated Any | Boolean to filter keys translated in any language. |
| - Filter Translated In Language | Comma-separated languages to filter keys translated in those languages. |
| - Filter Untranslated Any | Boolean to filter keys untranslated in any language. |
| - Filter Untranslated In Language | Comma-separated languages to filter keys untranslated in those languages. |
| - Structure Delimiter | String delimiter used for nested structure in export format (default is "."). |
| - Support Arrays | Boolean indicating whether to support arrays in export. |
| - Zip | Boolean indicating whether to return the export as a ZIP file. |
Output
The node outputs the exported translation data in the json field of the output items.
- If a single language is selected, the output contains the translation data in the chosen format (e.g., JSON, PO, XLIFF) as a string or structured object depending on the format.
- If multiple languages are selected or if the "Zip" option is enabled, the output will be a ZIP archive containing separate files for each language.
- Binary data output (ZIP file) is provided when exporting multiple languages or when explicitly requested via options.
Dependencies
- Requires an API key credential for authenticating with the Tolgee API.
- Needs the Tolgee project domain URL configured in credentials.
- The node uses HTTP requests to Tolgee's REST API endpoints to fetch projects, languages, and export data.
- Proper permissions on the Tolgee API key are necessary to access project export functionality.
Troubleshooting
- Failed to load languages/projects/namespaces: This usually indicates invalid or missing API credentials, incorrect domain URL, or insufficient permissions. Verify the API key and domain configuration.
- Empty or missing export data: Check that the project ID and language selections are correct and that there is translation data available matching the applied filters.
- Export format not supported or invalid: Ensure the selected format is one of the supported options listed in the properties.
- ZIP file not generated when expected: Confirm that multiple languages are selected or the "Zip" option is enabled.
- API rate limits or network errors: These may cause request failures; retry after some time or check network connectivity.