Description:

The Translate Text (Google Translate) step enables a FlowWright workflow to translate text in real time by using the Google Translate service.

Business workflows frequently need to communicate with users, customers, suppliers, or partners who speak different languages. This step accepts source text, optionally accepts the source language, translates the content into a selected target language, and stores the translated text in a workflow variable or global variable.

The translated output can then be used in emails, workflow forms, notifications, reports, customer communications, document generation, or integrations with external systems.

Typical uses include:

• Translating email notifications
• Creating multilingual workflow forms
• Translating customer requests
• Preparing multilingual reports
• Localizing approval comments
• Translating chatbot responses
• Generating multilingual document content
• Translating workflow variables before external integrations

This step allows organizations to automate multilingual communication without requiring manual translation activities.

Usage:

The Translate Text (Google Translate) step is typically used before sending user-facing communications or processing multilingual business content.

During execution:

1. Read the source text.
2. Determine the source language if one has been specified.
3. Submit the text to the Google Translate service.
4. Translate the text into the selected target language.
5. Store the translated result in the configured workflow variable or global variable.
6. Continue workflow execution through either the True or False return path.

A typical workflow might look like this:

Typical workflow scenarios include:

• Translating customer support requests
• Sending multilingual workflow notifications
• Localizing approval comments
• Translating survey responses
• Preparing multilingual invoices
• Translating generated reports
• Creating multilingual portal content
• Translating messages before REST API integrations

Example:

Let’s build and execute the “GoogleTranslateDef” example.

• Create a new process definition called “googleTranslateDef” and open it in Designer mode. 
• Drag a “GoogleTranslate” step to the canvas.
• Connect the dots between the “Start” step and “GoogleTranslate” steps, as shown above.
• Define a variable or a global to store the translated text. 
• Click the “GoogleTranslate” step to configure its “Required” properties. Provide a name for the step. Enter the text in a non-English language to translate. Select the source language from the drop-down list. Provide the variable or global reference to store the translated text at run-time. Click the Save button. Note: Click the "AI Predict" button for the Copilot to add new process steps that match your process description. 

• Click the “GoogleTranslate” step to configure its “Optional” properties. Select the source language from the drop-down list. Then click the Save button. 

• The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. This is achieved by configuring the step state and percent fields individually, as shown below. Configure the “Logging” using the following properties.

• Save the process definition, create a process instance, and execute it. The Step should translate text in real time into other languages, powered by Google. Select the process instance to render and verify the step properties.

Tips:

• Specify the source language whenever it is known to improve translation accuracy.
• Store translated text in reusable workflow variables for downstream workflow activities.
• Validate language selections before runtime when workflows support multiple locales.
• Route the False execution path to logging and notification activities for easier troubleshooting.
• Translate only the content that requires localization to reduce unnecessary processing.
• Combine this step with Send Email, Generate PDF, Ask AI, REST Call, Update Variable Values, or document generation steps to build multilingual business workflows.

Notes:

• The step accepts multiline text as input.
• The source language is optional.
• The target language is required.
• The translated text is stored in the configured workflow variable or global variable.
• The original input text is not modified.
• Both the True and False return paths should be implemented for complete workflow handling.
• Ensure that the Google Translate integration is properly configured before executing this step.
• Translation execution details are recorded in the FlowWright workflow execution log.

Translate Text (Google Translate) vs. Translate Text (Azure ML Language Translator):

Although both workflow steps provide automatic language translation, they integrate with different cloud translation services.

As a general guideline:

• Use Translate Text (Google Translate) when your FlowWright environment is integrated with Google Cloud translation services or when Google Translate is the preferred translation provider.
• Use Translate Text (Azure ML Language Translator) when your organization standardizes on Microsoft Azure Cognitive Services or when automatic source language detection using the default AutoDetect option is preferred.

Definition Sample:

You may download the sample workflow definition from the link provided and import it into your FlowWright environment.

Note: Verify and complete any missing configuration after importing the sample, including:

• Source text
• Source language (optional)
• Target language
• Workflow variable or global variable for the translated text
• Success and failure workflow branches
• Google Translate service configuration and credentials

After verifying the configuration, save and publish the workflow before execution.

Click here to download the sample file.