The IBM Watson Language Translator Service Spoke has been deprecated by IBM. This information is provided for legacy context. Customers with existing spoke installations can continue to use the translator service until it is withdrawn by IBM.

Important: IBM has announced the deprecation of the IBM Watson Translator Service for IBM Cloud in all regions. As of June 10, 2023, the Language Translator tile will be removed from the IBM Cloud Platform for new customers; only existing customers will be able to access the product. As of June 10, 2024, the service will reach its End of Support date. As of December 10, 2024, the service will be withdrawn entirely and will no longer be available to any customers. For more information, see https://cloud.ibm.com/docs/language-translator?topic=language-translator-release-notes.

Activation

Activate the Dynamic Translation plugin (com.glide.dynamic_translation) or the IBM Watson Language Translator Service Spoke plugin (com.glide.ibm_translation_spoke).

Subscription

This spoke requires any ServiceNow subscription that is Professional or above, and includes Dynamic Translation.

Supported versions

API version v3.

Spoke subflows

The spoke provides subflows in the Published state to integrate with the IBM Watson Language translation services. These subflows can be used as part of other subflows and flows.

Table 1. Spoke subflows
Subflow Description
Detect Language [detect_language_v3] Contains a set of inputs, actions, and output to detect the language of the input text.
Translate Text [translate_text_v3] Contains a set of inputs, actions, and outputs to translate the input text to multiple languages.

Spoke actions

The spoke provides actions to integrate with IBM translation services.

Table 2. Spoke actions
Action Description
Detect Language [detect_language_v3] Detects the language of the input text.
Translate Text [translate_text_v3] Translates the input text to multiple languages.

IBM account requirements

For information on the IBM Language Translator API and the notice of deprecation, see the IBM documentation.

Connection and credential alias requirements

IntegrationHub uses aliases to manage connection and credential information. Using an alias eliminates the need to configure multiple credentials and connection information profiles when using multiple environments. If the connection or credential information changes, you do not need to update any actions that use the connection. For more information, see Credentials and connection information.

To use the spoke connection aliases, create an associated connection record and a credential record for each alias.

This spoke uses the IBMTranslation alias (sn_ibm_trans_spoke.IBMTranslation) to authorize actions.

The following are the connection alias requirements.
  • Connection type: HTTP
  • Connection URL: Base URL provided by IBM to connect to the language translator service. Users can have a different URL based on their geographical preference.

Perform the following tasks to connect to the IBM Watson Language translation services and use them to translate the dynamically generated text.