DeepL Translation connector.

Translate one text passage with DeepL and read API usage through separate, bounded actions.

Download connector See all connectors

Connector download

Download DeepL Translation

Versioned ZIP for your CXFabric tenant.

Register the ZIP in your tenant, or add a new version if the connector is already installed.
Create or select a credential if the action requires one.
In a Draft flow, add an available action, choose its version, connect it, and map inputs.
Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Included in this version

Implemented in v0.1.0.0. Use a separate flow trigger; no webhook trigger is included.

Translate one passage and return translated text and detected source language.

Read current character count and character limit for the selected key.

Vendor API

Implementation considerations

Supported scope: Translate one text passage with DeepL and read API usage through separate, bounded actions.
Select a bearer-token credential containing the DeepL API key. It is sent with the DeepL-Auth-Key prefix. Choose the API Free or API Pro HTTPS origin in flow properties; only those two documented origins are accepted.
One text passage per translation, up to 10000 characters and within the 128 KiB request limit. No document upload, glossary, admin key management or batch polling. Translation can consume billable quota; a timeout does not prove the provider did not process the text. Each HTTP action uses a 1–8 second request budget, a 128 KiB request-body limit and a 1 MiB raw JSON response limit. Redirects, automatic paging and automatic retries are disabled. Responses exceeding these bounds fail rather than being truncated. Configure only trusted HTTPS service origins and map connection settings from flow properties.
New independent connector registration. Existing legacy flows require deliberate action and credential remapping. Hosted import and live service validation remain pending.