MENU
    Translate Trigger Action
    • 03 May 2024
    • 3 Minutes to read
    • Contributors

    Translate Trigger Action


    Article summary

    Purpose

    The Translate{{glossary.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:

    • Unifying 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

    Input: Text

    This is the text that will be translated. “Translate” automatically infers the language of the text.

    Supported data type
    InputText

    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.

    Supported data type
    InputText

    Automation Action - Inputs and outputs

    The automations action has two inputs, Text and Target language, and one output, the translated text.

    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
    InputText

    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.

    Supported data type
    InputText

    Supported Languages

    The following languages are supported for Text and Target Language.

    Language codeLanguage
    BGBulgarian
    CSCzech
    DADanish
    DEGerman
    ELGreek
    EN-GBEnglish (British)
    EN-USEnglish (American)
    ESSpanish
    ETEstonian
    FIFinnish
    FRFrench
    HUHungarian
    IDIndonesian
    ITItalian
    JAJapanese
    KOKorean
    LTLithuanian
    LVLatvian
    NBNorwegian (Bokmål)
    NLDutch
    PLPolish
    PT-BRPortuguese (Brazilian)
    PT-PTPortuguese (all Portuguese varieties excluding Brazilian Portuguese)
    RORomanian
    RURussian
    SKSlovak
    SLSlovenian
    SVSwedish
    TRTurkish
    UKUkrainian
    ZHChinese (simplified)

    Output: Translated Text

    The trigger action and automation action each returns the translated text.

    Supported data type
    OutputText

    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 {{glossary.Instance}} level. In a case where these limits have been exceeded, the translate trigger action will fail.

    Monthly Limit: No limit
    Rate Limit: 10 Requests/Minute
    Plain text

    Account Usage Limit: See details here


    Was this article helpful?