The Translate - Text task task lets you translate an input text using Cloud Translation. Input text can be a plain text or a HTML.
Cloud Translation is a Google Cloud service that allows you to translate text for more than 100 language pairs with the capability of auto language detection. For a list of all supported languages, see Supported languages.
Before you begin
Ensure that you perform the following tasks in your Google Cloud project before configuring the Translate - Text task:
Enable the Cloud Translation API (translate.googleapis.com).
Create an authentication profile. Application Integration uses an authentication profile to connect to an authentication endpoint for the Translate - Text task task.
The Integrations page appears listing all the integrations available in the Google Cloud project.
Select an existing integration or click Create integration to create a new one.
If you are creating a new integration:
Enter a name and description in the Create Integration pane.
Select a region for the integration.
Select a service account for the integration. You can change or update the service account details of an integration any time from the infoIntegration summary pane in the integration toolbar.
Click Create. The newly created integration opens in the integration editor.
In the integration editor navigation bar, click Tasks to view the list of available tasks and connectors.
Click and place the Translate - Text element in the integration editor.
Click the Translate - Text element on the designer to view the Translate - Text task configuration pane.
Go to Authentication, and select an existing authentication profile that you want to use.
Optional. If you have not created an authentication profile prior to configuring the task, Click + New authentication profile and follow the steps as mentioned in Create a new authentication profile.
Go to Task Input, and configure the displayed inputs fields using the following Task input parameters table.
Changes to the inputs fields are saved automatically.
Task input parameters
The following table describes the input parameters of the Translate - Text task:
Property
Data type
Description
Region
String
Region where you want to run the translate operation. For example, us-central1.
ProjectsId
String
Your Google Cloud project ID.
Request
JSON
See request JSON structure. To translate multiple input texts, specify the strings in the contents field of the request body. For example, "contents": ["Hello World", "This is an example text"].
Task output
The Translate - Test task returns the translated output text, similar to the following sample output:
{
"translations": [
{
"translatedText": "Bonjour le monde",
},
{
"translatedText": "Ceci est un exemple de texte",
}
]
}
Error handling strategy
An error handling strategy for a task specifies the action to take if the task fails due to a temporary error. For information about how to use an error handling strategy, and to know about the different types of error handling strategies, see Error handling strategies.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[[["\u003cp\u003eThe Translate - Text task in Application Integration allows you to translate text using the Cloud Translation service, supporting over 100 language pairs with auto language detection.\u003c/p\u003e\n"],["\u003cp\u003eThis feature is currently in Pre-GA status, meaning it is available "as is" with potentially limited support, as described in the Pre-GA Offerings Terms and launch stage descriptions.\u003c/p\u003e\n"],["\u003cp\u003eTo use the Translate - Text task, you must enable the Cloud Translation API and create an authentication profile within your Google Cloud project.\u003c/p\u003e\n"],["\u003cp\u003eThe task accepts plain text or HTML as input, and while it does not translate HTML tags, the order of tags may change in the translated output due to linguistic variations.\u003c/p\u003e\n"],["\u003cp\u003eInput parameters for the Translate - Text task include region, project ID, and a JSON request body specifying the text to be translated, with multiple texts supported in the \u003ccode\u003econtents\u003c/code\u003e field.\u003c/p\u003e\n"]]],[],null,["# Translate - Text task\n\nSee the [supported connectors](/integration-connectors/docs/connector-reference-overview) for Application Integration.\n\nTranslate - Text task\n=====================\n\n|\n| **Preview**\n|\n|\n| This feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nThe **Translate - Text task** task lets you translate an input text using Cloud Translation. Input text can be a plain text or a HTML.\n\n[Cloud Translation](/translate/docs/overview) is a Google Cloud service that allows you to translate text for more than 100 language pairs with the capability of auto language detection. For a list of all supported languages, see [Supported languages](/translate/docs/languages).\n| **Note:**\n|\n| - Cloud Translation does not translate any HTML tags that are provided in the input HTML. The translated output retains the (untranslated) HTML tags and only translates the text within the HTML tags.\n| - The order of HTML tags in the translated output may differ from the order present in the input HTML due to linguistic order changes in the translation.\n\nBefore you begin\n----------------\n\nEnsure that you perform the following tasks in your Google Cloud project before configuring the **Translate - Text** task:\n\n1. Enable the Cloud Translation API (`translate.googleapis.com`).\n\n\n [Enable the Cloud Translation API](https://console.cloud.google.com/flows/enableapi?apiid=translate.googleapis.com)\n2. Create an [authentication profile](/application-integration/docs/configuring-auth-profile#createAuthProfile). Application Integration uses an authentication profile to connect to an authentication endpoint for the **Translate - Text task** task.\n\n For information about granting additional roles or permissions to a service account, see [Granting, changing, and revoking access](/iam/docs/granting-changing-revoking-access).\n\nConfigure the Translate - Text task\n-----------------------------------\n\n1. In the Google Cloud console, go to the **Application Integration** page.\n\n [Go to Application Integration](https://console.cloud.google.com/integrations)\n2. In the navigation menu, click **Integrations** .\n\n\n The **Integrations** page appears listing all the integrations available in the Google Cloud project.\n3. Select an existing integration or click **Create integration** to create a new one.\n\n\n If you are creating a new integration:\n 1. Enter a name and description in the **Create Integration** pane.\n 2. Select a region for the integration. **Note:** The **Regions** dropdown only lists the regions provisioned in your Google Cloud project. To provision a new region, click **Enable Region** . See [Enable new region](/application-integration/docs/enable-new-region) for more information.\n 3. Select a service account for the integration. You can change or update the service account details of an integration any time from the info **Integration summary** pane in the integration toolbar. **Note:** The option to select a service account is displayed only if you have enabled integration governance for the selected region.\n 4. Click **Create** . The newly created integration opens in the *integration editor*.\n\n\n4. In the *integration editor* navigation bar, click **Tasks** to view the list of available tasks and connectors.\n5. Click and place the **Translate - Text** element in the integration editor.\n6. Click the **Translate - Text** element on the designer to view the **Translate - Text** task configuration pane.\n7. Go to **Authentication** , and select an existing authentication profile that you want to use.\n\n Optional. If you have not created an authentication profile prior to configuring the task, Click **+ New authentication profile** and follow the steps as mentioned in [Create a new authentication profile](/application-integration/docs/configuring-auth-profile#createAuthProfile).\n8. Go to **Task Input** , and configure the displayed inputs fields using the following [Task input parameters](#params) table.\n\n Changes to the inputs fields are saved automatically.\n\nTask input parameters\n---------------------\n\n\nThe following table describes the input parameters of the **Translate - Text** task:\n\nTask output\n-----------\n\nThe **Translate - Test** task returns the translated output text, similar to the following sample output: \n\n```\n{\n \"translations\": [\n {\n \"translatedText\": \"Bonjour le monde\",\n },\n {\n \"translatedText\": \"Ceci est un exemple de texte\",\n }\n ]\n}\n```\n\n\u003cbr /\u003e\n\nError handling strategy\n-----------------------\n\n\nAn error handling strategy for a task specifies the action to take if the task fails due to a [temporary error](/application-integration/docs/error-handling). For information about how to use an error handling strategy, and to know about the different types of error handling strategies, see [Error handling strategies](/application-integration/docs/error-handling-strategy).\n\nQuotas and limits\n-----------------\n\nFor information about quotas and limits, see [Quotas and limits](/application-integration/docs/quotas).\n\nWhat's next\n-----------\n\n- Add [edges and edge conditions](/application-integration/docs/edge-overview).\n- [Test and publish](/application-integration/docs/test-publish-integrations) your integration.\n- Configure a [trigger](/application-integration/docs/how-to-guides#configure-triggers).\n- Add a [Data Mapping task](/application-integration/docs/data-mapping-task).\n- See [all tasks for Google Cloud services](/application-integration/docs/how-to-guides#configure-tasks-for-google-cloud-services)."]]