Skip to content

DeepL

DeepL is an artificial intelligence (AI) company that specializes in language translation services. It offers a neural machine translation (NMT) engine capable of providing high-quality translations across multiple languages. DeepL’s translation engine is known for its accuracy, natural-sounding translations, and ability to understand context.

Before setting up

Before you can connect you need to make sure that:

  • You have a DeepL account.
  • You have an API key for your DeepL account. It can be found under account settings in DeepL.
  • Important: If you are using an API key for CAT tools, it will not work for the public API. Instead, you need to use the Authentication key for DeepL API. You can find guidance on where it is located in this guide. For more details, you can also refer to this discussion, where a similar issue was resolved.

Connecting

  1. Navigate to Apps, and identify the DeepL app. You can use search to find it.
  2. Click Add Connection.
  3. Name your connection for future reference e.g. ‘My DeepL connection’.
  4. Fill in the API key to your DeepL account.
  5. Click Connect.

DeepLBlackbirdConnection

Actions

Translation

  • Translate Translate text
  • Translate document Translate a document, including XLIFF files (1.2 or 2.1 version)

Glossaries

  • Export glossary Export glossary
  • Import glossary Import glossary (.tbx, .csv & .tsv)
  • Get glossary Get details of a specific glossary
  • Get glossary entries Get glossary entries in a TSV format
  • List glossaries List all glossaries
  • List glossary language pairs List supported glossary language pairs

Example

DeepLExample

The example above shows a bird that is triggered as soon as an article is published in Zendesk, said article is then exported as an HTML document and translated through DeepL before being imported back into Zendesk. The DeepL translation also considers as guardrail a Glossary that has been exported from Microsoft Excel.

Feedback

Do you want to use this app or do you have feedback on our implementation? Reach out to us using the established channels or create an issue.