The new DeepL Connector complements the existing translation functionality in Operation1 with an additional translation provider. Furthermore, it allows the possibility to add a glossary for company-specific terminology.
Benefits
DeepL provides high-quality translations.
Using the connector enables a consistent corporate language through the use of a glossary.
DeepL is a German provider and meets strict data protection requirements.
Use Cases
Translations, especially of technical terms, can be corrected and aligned as needed.
Enables uniform and consistent translation of technical terminology.
Setting up the DeepL Connector
Step 1: Open the Connector Section
Navigate to the system settings and click on “Connectors” in the menu.
Step 2: Add the DeepL Connector
Via “Add Connector”, select “DeepL Connector” from the dropdown menu.
Step 3: Configure the Connector
To configure the DeepL Connector, only an API key is required; an optional description can be added.
Using the Connector Requires Access to the DeepL API
To activate API access, an appropriate DeepL account is required. You can initially use the free API plan.
With the free API access, a glossary can be created and a limited number of characters are available for translation each month via the DeepL API. If the free plan is not sufficient, a paid subscription can be purchased from DeepL to obtain unlimited API access.
Defining and Managing a Glossary
Glossaries are managed via DeepL. In the DeepL interface, language pairs can be defined for translation. Within each language pair, terms in the source and target language can be added. To ensure terms are translated correctly in Operations1 according to the glossary, they must match the terms stored in DeepL exactly.
For more information about the glossary feature in DeepL, click here.
Once a valid API key is entered, the desired glossary can be selected from the dropdown menu.
If an invalid API key is entered, an error message will appear in the configuration view.
Translating Documents with the DeepL Connector
Once the DeepL Connector is activated, it is used instead of the Azure service for automated translations.
The use does not differ from the existing AI-based translation. Detailed instructions for how to use the automatic AI-based translations can be found here.
If a target language selected in Operations1 is not supported by DeepL or if there is no suitable glossary for a language combination, corresponding error messages will appear. In these cases, the translation will be performed using the Azure translation service.