DeepL integration

What it does

The DeepL integration lets your agency call DeepL's neural translation API from inside any workflow. Connect a client's DeepL API key once and your workflows can translate inbound form submissions before they reach a CRM, localize outbound emails per recipient locale, kick off document translation jobs and poll for completion, apply client-managed glossaries to keep terminology consistent across languages, and pull current usage so a workflow can branch on remaining quota.

Connect a DeepL account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose DeepL and click Connect.
3. In a new tab, open the DeepL account summary page signed in as the client (or as your agency, if the client has delegated key management to you).
4. Copy the Authentication Key. Free keys are suffixed with :fx and target api-free.deepl.com. Pro keys carry no suffix and target api.deepl.com.
5. Paste the key and the matching host (api-free.deepl.com for DeepL API Free, api.deepl.com for DeepL API Pro) into TaskJuice and save the connection.

To rotate or revoke the key later, return to the DeepL account summary page, create a new key, update the TaskJuice connection, and delete the old key.

Triggers

DeepL does not publish a public webhook surface, so the integration is action-only per the AI-provider exception in the catalog policy. Use a Schedule, a polling trigger from another app, or an inbound webhook from a different source to invoke DeepL actions inside a workflow.

Actions

• deepl/translate-text translates one or more strings into a target language, with optional source language, formality, glossary, and tag-handling controls.
• deepl/get-document-status polls the translation status of a document previously uploaded to DeepL, returning progress, remaining seconds, and billed character count.
• deepl/get-usage returns the current period's character count and character limit for the connected key, useful for branching on remaining quota.
• deepl/list-glossaries returns every glossary on the connected account, including ID, language pair, ready status, and entry count.
• deepl/delete-glossary deletes a glossary by ID.

Known limitations

• The integration calls the DeepL REST API with the connected key. Per-key rate limits, character quotas, and language-pair availability are governed by the client's DeepL subscription, not by TaskJuice. When DeepL returns a 429 or 456, TaskJuice surfaces them as rate-limit and quota-exceeded errors respectively.
• DeepL splits Free and Pro keys across separate hosts (api-free.deepl.com vs api.deepl.com). Each connection targets one tier, so a client that moves from Free to Pro needs a new connection with the Pro key and host.
• Document translation is asynchronous. The upload step returns a document ID and key, and a workflow polls deepl/get-document-status until status is done before downloading the result.
• Glossary creation is not exposed as a first-class action yet. Use the DeepL web app or the underlying API directly to create glossaries; list and delete are supported in-workflow.