|
| 1 | +# Intento Enterprise Language Hub |
| 2 | + |
| 3 | +**Author:** [Intento Inc.](https://inten.to) |
| 4 | + |
| 5 | +## Description |
| 6 | +The Intento Enterprise Language Hub provides access to over 20 machine translation systems, including custom models, smart routing mechanisms, and various tweaking abilities for pre- and post-processing. This extension allows you to leverage the Enterprise Language Hub directly within the Cognigy Platform. To use this extension, a commercial API key for Intento MT Hub is required. Please obtain one from [Intento Console](https://console.inten.to). |
| 7 | + |
| 8 | +## Table of Contents |
| 9 | +1. [Installation](#installation) |
| 10 | +2. [Usage](#usage) |
| 11 | +3. [Nodes](#nodes) |
| 12 | + - [Detect Language](#detect-language) |
| 13 | + - [Translate](#translate) |
| 14 | +4. [Support](#support) |
| 15 | +5. [License](#license) |
| 16 | + |
| 17 | +## Installation |
| 18 | +To install or import the Intento Enterprise Language Hub package into your Cognigy.AI platform, follow these steps: |
| 19 | +1. Navigate to the Extensions section in the Cognigy.AI interface. |
| 20 | +2. Find the Extension in the Cognigy Marketplace or click on "Upload Extension" button and select the Intento Enterprise Language Hub package. |
| 21 | +3. Follow the on-screen instructions to complete the installation process. |
| 22 | + |
| 23 | +## Usage |
| 24 | +### Basic Usage Instructions |
| 25 | +1. Ensure you have a valid Intento API key. You can get one from the [Intento Console](https://console.inten.to). |
| 26 | +2. Use the provided nodes to detect languages and translate text within your Cognigy.AI flows. |
| 27 | + |
| 28 | +## Nodes |
| 29 | + |
| 30 | +### Detect Language |
| 31 | +This node detects the language of a given text. |
| 32 | + |
| 33 | +#### Input Parameters: |
| 34 | +- **Connection**: Intento API key |
| 35 | +- **Text**: The text for language detection |
| 36 | +- **Language detection provider**: The language detection provider. Supported providers include Google, Support, IBM. Microsoft is set by default. |
| 37 | +- **Store location**: The location where the result of language detection should be stored. The language ISO code is returned. |
| 38 | + |
| 39 | +### Translate |
| 40 | +This node translates a given text from a source language to a target language. |
| 41 | + |
| 42 | +#### Input Parameters: |
| 43 | +- **Connection**: Intento API key |
| 44 | +- **Text to translate**: The text string that needs to be translated |
| 45 | +- **Source language code**: The language ISO code of the source language (can be empty). |
| 46 | +- **Target language code**: The language ISO code of the target language (cannot be empty). |
| 47 | +- **Intento routing**: Intento routing table name. Default is Intento best routing. |
| 48 | +- **Store location**: The location where the result of the translation should be stored. |
| 49 | +- **Additional logging**: Enable additional logging on the Intento backend side (disabled by default). Reveals the text of the payload. |
| 50 | +- **Translation Storage**: Enable cache on the Intento backend side. |
| 51 | +- **Translation Storage Instance**: Allows filtering Translation Storage entries by instance ID. Default is the Cognigy profile ID. |
| 52 | + |
| 53 | +## Support |
| 54 | +For any issues or questions regarding the Intento Enterprise Language Hub, please contact Intento Inc. support at [[email protected]](mailto:[email protected]). |
0 commit comments