AWS Translate Spoke

  • Release version: Zurich
  • Updated June 16, 2026
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of AWS Translate Spoke

    The AWS Translate spoke enables ServiceNow customers to integrate their instances with AWS Translate and AWS Comprehend services. This integration allows automatic detection of text languages and translation of text into desired languages within ServiceNow workflows. It is designed to support efficient multilingual communication and automation of translation tasks triggered by ServiceNow events.

    Show full answer Show less

    Key Features

    • Language Detection: Uses AWS Comprehend to detect the dominant language of provided text, returning a confidence score and language details that can be used in subsequent flow actions.
    • Text Translation: Translates text from a source language to a target language using AWS Translate. Supports automatic source language detection when configured with a compatible region.
    • Sample Flow Provided: Includes a ready-to-use example flow that translates an incident’s short description to Spanish upon creation, which can be customized to meet specific requirements.
    • Integration Hub Dependency: Requires an active Integration Hub subscription and specific dependent plugins to function properly.
    • Connection Management: Supports connection and credential aliasing to streamline management of credentials across different environments without the need to reconfigure actions.

    Requirements and Compatibility

    • User must have full AWS Translate access credentials (Access Key ID and Secret Access Key).
    • Supports AWS Translate API version 2017-07-01 and AWS Comprehend version 2017-11-27; later API versions may be compatible but require validation.
    • Not compatible with dynamic translation in its current version.
    • Dependent plugins include Complex Object, IntegrationHub Runtime, Flow Designer - Dynamic Inputs, and IntegrationHub Action Step - REST, some of which require licensing.

    Practical Benefits

    ServiceNow customers can automate language detection and translation directly within their incident or workflow processes, improving communication and reducing manual translation effort. The spoke’s design facilitates easy setup and customization, helping to localize user interactions and support multilingual environments effectively.

    Integrate your ServiceNow instance with AWS Translate to detect languages in the text and translate text to the required language.

    Request apps on the Store

    Visit the ServiceNow Store website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.

    Integration Hub subscription

    This spoke requires an Integration Hub subscription. For more information, see Legal schedules - IntegrationHub overview.

    Supported version

    This spoke was built for AWS Translate API version 2017-07-01 and AWS Comprehend version 2017-11-27, but may be compatible with later versions.
    Note:
    • If you use different API version, ensure that you change the API version in all spoke actions.
    • The current version of the AWS Translate spoke is not compatible with dynamic translation.

    Spoke dependencies

    If you’re having trouble installing the app, ensure that these dependent plugins are installed:

    • Complex Object (com.glide.cobject)
    • ServiceNow IntegrationHub Runtime (com.glide.hub.integration.runtime)
    • ServiceNow Flow Designer - Dynamic Inputs (com.glide.hub.dynamic_inputs)
    • ServiceNow IntegrationHub Action Step - REST (com.glide.hub.action_step.rest)
    Note:
    Some of these plugins are licensable features and require an appropriate license if used outside the spoke implementation. For information on licenses, contact your account manager.

    Spoke requirements

    • User with full access to AWS Translate.
    • Access Key ID and Secret Access Key of the user. Record these values for later use. For more information, see Create an access key.
    For more information about creating user and providing the required access, see AWS Identity and Access Management Documentation site.

    Spoke flow

    The AWS Translate spoke provides a sample flow, Translate Short Description when Incident is Created to demonstrate translating the short description to Spanish when an incident is created. You can customize the sample flow as per your requirement by creating a copy of it in the required scope.

    Spoke actions

    The AWS Translate spoke provides actions to automate translating tasks when events occur in ServiceNow. Available actions include:
    Category Action Description
    Language Management Detect Dominant Language Detects the language of text using AWS Comprehend service.
    Note:
    Provide the text for which you want to detect the dominant language in the action input Text. The output is a JSON string that contains an array of the detected languages. One of the elements in the array is Score. This is a decimal number and its value is between 0 and 1.
    Using Score in subsequent actions.

    When the action is executed, the Languages Detected action output may not display any runtime value. However, the output data pill still holds the response data and can be used in the subsequent actions in the flow or subflow.

    Score value in the output response body.
    Translate Management Translate Text Translates text from the source language to the target language using AWS Translate service.
    Note:
    • For Source Language and Target Language, input values can’t be selected until a valid input value is provided for Region.
    • If you select Auto from the Source Language list, the AWS Translate API uses the AWS Comprehend service to automatically detect the language. In this case, you must provide the region that supports Amazon Comprehend. Else, the request returns an error indicating the auto-detect is not supported.
    Note:
    The actions have Region as an input. To retrieve the list of available regions, use the List Regions action from the Amazon EC2 Spoke.

    Connection and credential alias requirements

    Integration Hub uses aliases to manage connection and credential information, and OAuth credentials. 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 don't need to update any actions that use the connection.

    For information about setting up the spoke, see Set up the AWS Translate spoke.