--- title: "Translate trigger action" slug: "translate" status: "update" updated: 2026-05-21T18:53:21Z published: 2026-05-21T18:53:21Z canonical: "support.tulip.co/translate" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.tulip.co/llms.txt > Use this file to discover all available pages before exploring further. # Translate trigger action The Translate Action is powerful, but simple. Provide text along with a target output language and this trigger action will return translated text. The source language is automatically detected based on the text that is provided. ### Example use cases Modern manufacturing takes place across countries and languages. It conforms to the language where your users are most comfortable, which is critical to drive the best possible insights. Some example use cases include: - **Unify the notes added along with defect reports to one target language.** Users can enter their description of the underlying issue in their native language, and it will automatically be translated to the language spoken by key stakeholders. - **Message between employees, respecting each of their native languages.** Lookup the desired language of the recipient, and translate any messages to that user into their target language without any overhead for the user sending that message. - **Translate information from other business systems into user native language.** The packaging notes returned from your ERP are critical to ensure no defects are created, but these notes are complex. Translate them into the native language of your users on the fly to reduce the risk of these defects. ## Trigger action - Inputs and outputs The trigger action has two inputs, Text and Target language, and one output, the translated text. ![image.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%28206%29.png) ### Input: text This is the text that will be translated. “Translate” automatically infers the language of the text. | | Supported data type | | --- | --- | | Input | Text | ### Input: target language This is the language the text should be translated into. The input should be in ISO 639-1 format as shown in the “Supported values” list [below](/r230/docs/translate#supported-languages). | | Supported data type | | --- | --- | | Input | Text | ## Automation action: inputs and outputs The automations action has two inputs, Text and Target language, and one output, the translated text. ![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/image%28404%29.png) ### Input: text This is the text that will be translated. “Translate” automatically infers the language of the text. This can reference any Text variable within the context of the respective automation. | | Supported data type | | --- | --- | | Input | Text | ### Input: target language This is the language the text should be translated into. The input should be in ISO 639-1 format as shown in the “Supported values” list below. This can reference any Text variable within the context of the respective automation. See the list of supported language codes [below](/r230/docs/translate#supported-languages). | | Supported data type | | --- | --- | | Input | Text | ## Supported languages The following languages are supported for **Text** and **Target Language**. | Language code | Language | | --- | --- | | BG | Bulgarian | | CS | Czech | | DA | Danish | | DE | German | | EL | Greek | | EN-GB | English (British) | | EN-US | English (American) | | ES | Spanish | | ET | Estonian | | FI | Finnish | | FR | French | | HU | Hungarian | | ID | Indonesian | | IT | Italian | | JA | Japanese | | KO | Korean | | LT | Lithuanian | | LV | Latvian | | NB | Norwegian (Bokmål) | | NL | Dutch | | PL | Polish | | PT-BR | Portuguese (Brazilian) | | PT-PT | Portuguese (all Portuguese varieties excluding Brazilian Portuguese) | | RO | Romanian | | RU | Russian | | SK | Slovak | | SL | Slovenian | | SV | Swedish | | TR | Turkish | | UK | Ukrainian | | ZH | Chinese (simplified) | ### Output: translated text The trigger action and automation action each returns the translated text. | | Supported data type | | --- | --- | | Output | Text | ## Error types #### No text to translate provided If no text to translate is provided to the trigger action, an empty string will be returned. #### Unsupported input text language The trigger action will try to interpret the text as one of the supported languages. Depending on the input, this can either lead to text being translated inaccurately or the input text being returned as the translated text. #### No target language provided If no target language is provided to the trigger action, the App will show the following system error: *Target language for translation not provided. Contact your Tulip administrator for support.* This happens for both of the following cases: - The target language input does not have a value assigned. This is equivalent to “null”. - The target language input has an empty string assigned. #### Unsupported or invalid target language provided If an unsupported invalid target language is provided, the App will show the following system error: *An invalid ISO 639-1 language codec was provided for the translation trigger. Contact your Tulip administrator for support.* ## Limits Warning Limits are subject to change. Currently, the following limits exist for Translate triggers. These limits are tracked on an Instance level. If these limits have been exceeded, the translate trigger action will fail. | | Limit | | --- | --- | | Monthly limit | None | | Rate limit | 10 requests per minute | For additional limits, including account usage, see [Tulip AI usage and pricing](https://support.tulip.co/docs/tulip-ai-usage-and-pricing). --- Did you find what you were looking for? You can also head to [community.tulip.co](https://community.tulip.co/?utm_source=intercom&utm_medium=article-link&utm_campaign=all) to post your question or see if others have solved a similar topic! **Action** **Actions**are different operations that can be executed in **Triggers. Actions**cannot move users to other apps, or other**steps.** Many **Actions**can be added to a single **Trigger.** *ex. Store the value of variable x to table field y, Print app step, Adjust Edge device GPIO pin.* **Tulip Instance** A Tulip customer account. Your instance can be found at https://[your-instance].tulip.co When *your instance*is referenced, we are just talking about your Tulip account on an organization-level, not user-level.