Actions5
- Translation Actions
- Import Actions
- Export Actions
Overview
This node integrates with the Tolgee API to create new translation keys and their corresponding translations within a specified Tolgee project. It is useful for managing multilingual content by programmatically adding translation entries, which can then be used in applications to support multiple languages.
Common scenarios include:
- Automating the addition of new translation keys during a CI/CD pipeline.
- Bulk importing translations from external sources.
- Dynamically creating translations based on user input or other workflows.
For example, you might use this node to add a new UI label key "welcome_message" with translations in English, Spanish, and French, so your app can display the appropriate text depending on the user's language.
Properties
| Name | Meaning |
|---|---|
| Project Name or ID | The ID of the Tolgee project where the translation key will be created. You can select from existing projects or specify an ID via expression. |
| Key Name | The unique name of the translation key to create (e.g., "welcome_message"). |
| Translations | A collection of translations for different languages. Each entry requires: • Language Name or ID (e.g., "en", "es") • Text: The actual translated string for that language. Multiple translations can be added. |
| Options | Additional optional settings: • Languages To Return Name or ID: Specify which languages' data should be returned after creation. • Namespace Name or ID: The namespace within the project to create the translation in. |
Output
The node outputs JSON data representing the newly created translation key along with its translations. The structure typically includes details such as the key name, associated translations per language, and metadata like namespaces if specified.
If binary data were involved (not indicated here), it would represent files or media related to translations, but this node focuses solely on JSON translation data.
Dependencies
- Requires an active Tolgee API connection configured with:
- The Tolgee API domain URL.
- An API authentication token (API key).
- The node uses Tolgee REST endpoints to fetch projects, languages, and namespaces dynamically.
- Proper permissions on the Tolgee project are necessary to create translation keys.
Troubleshooting
- Failed to load languages/projects/namespaces: This usually indicates incorrect API credentials, insufficient permissions, or network issues. Verify the API key and domain URL in the credentials.
- Missing required fields: Ensure that the Project ID, Key Name, and at least one translation with language and text are provided.
- Invalid language or namespace IDs: Use the dropdowns populated by the node or valid IDs from Tolgee to avoid errors.
- API rate limits or server errors: If the Tolgee API returns errors, check the service status and retry later.