IBM Watson Language Translator Service spoke

With the Xanadu release, the IBM Watson Language Translator Service Spoke is no longer available because it has been deprecated. This information is provided for legacy context. The spoke provided subflows and actions to dynamically translate user-entered texts and to detect the language of user-entered texts using the IBM translation service.

Important:

IBM announced the deprecation of the IBM Watson Translator Service for IBM Cloud in all regions. As of December 10, 2024, the service is withdrawn entirely and no longer available to any customers. For more information, see https://cloud.ibm.com/docs/language-translator?topic=language-translator-release-notes.

Activation

With the Xanadu release, the IBM Watson Language Translator Service Spoke is deprecated and is no longer available.

Before deprecation, this spoke was activated with 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 required any ServiceNow subscription that is Professional or above, and includes Dynamic Translation.

Supported versions

API version v3.

Spoke subflows

The spoke provided subflows in the Published state to integrate with the IBM Watson Language translation services. These subflows could 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 provided 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.

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

The following were 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.