---
sourceDocument: Xanadu ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/platform-administration

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# IBM Watson Language Translator Service spoke

# IBM Watson Language Translator Service spoke {#ariaid-title1}

* Release version: Xanadu
* 
* Updated January 6, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

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 {#ibm-translation-spoke__section_vxz_lhr_h1c}

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 {#ibm-translation-spoke__section_swc_v2t_3jb}

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

## Supported versions {#ibm-translation-spoke__section_gbp_mrt_shb}

API version v3.

## Spoke subflows {#ibm-translation-spoke__section_ylg_4rt_shb}

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.
{#ibm-translation-spoke__table_krq_5rt_shb__entry__2}

| 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. |
[Table 1. Spoke subflows]

{#ibm-translation-spoke__table_krq_5rt_shb}

## Spoke actions {#ibm-translation-spoke__section_uv5_prt_shb}

The spoke provided actions to integrate with IBM translation services.
{#ibm-translation-spoke__table_jd2_lst_shb__entry__2}

| 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. |
[Table 2. Spoke actions]

{#ibm-translation-spoke__table_jd2_lst_shb}

## IBM account requirements {#ibm-translation-spoke__section_v4d_dvt_shb}

For information on the IBM Language Translator API and the notice of deprecation, see the [IBM](https://cloud.ibm.com/apidocs/language-translator) documentation.

## Connection and credential alias requirements {#ibm-translation-spoke__section_pcy_f5t_shb}

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](https://www.servicenow.com/docs/access?context=r-credentials&version=xanadu&pubname=xanadu-platform-security&ft:locale=en-US).

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.
{#ibm-translation-spoke__ul_ivv_kjt_msb}

