--- title: "DeepL Integration" description: "Translate text and full documents with DeepL neural machine translation, improve writing with DeepL Write, and manage glossaries to keep terminology consistent across languages." url: https://flowrunner.ai/integrations/deepl date_modified: 2026-08-07T17:20:23-07:00 --- # DeepL [AI](https://flowrunner.ai/integrations/category/ai-llms) Translate text and full documents with DeepL neural machine translation, improve writing with DeepL Write, and manage glossaries to keep terminology consistent across languages. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 14 actions · API key · available [DeepL website](https://deepl.com/) · [Platform Documentation](https://developers.deepl.com/) · Capability data verified 2026-08-12 1. New support ticket arrives in a non-English language 2. Agent detects the source language of the ticket 3. Agent translates the ticket into the support team language 4. Agent applies the product glossary so terms translate consistently 5. Agent files the translated ticket with the original attached 6. Support agent gets the ticket in their language 7. A legally sensitive or high-value message routes to a bilingual reviewer ## What This Integration Enables DeepL covers the full translation surface a business needs. Text translation handles individual strings, document translation preserves the formatting of whole files, DeepL Write improves phrasing and tone, and glossaries lock in the correct rendering of your product and domain terms. Language detection means the flow figures out the source language on its own. Translation quality is table stakes; the value is making it operational. A ticket in another language should translate, route, and reach the right agent without a person shuffling files to a translator. An orchestration layer runs that end to end and pulls a bilingual reviewer in only where the stakes justify it, and FlowRunner is built for that layer. ### Without FlowRunner **Language a barrier**: Tickets and documents in other languages wait for a translator **Formatting lost**: Translated documents come back as unformatted text **Terms inconsistent**: Product names translate differently every time ### With FlowRunner **Language handled in the flow**: Text and documents translate the moment they arrive **Formatting preserved**: Document translation keeps layout intact **Terminology enforced**: Glossaries hold your terms consistent across languages ## Use Case Scenarios ### Multilingual Support Support tickets arrive in many languages. The agent detects each ticket's language, translates it into the support team's working language with the product glossary applied, and files it with the original attached. The agent replies in their language, and the response is translated back for the customer. Language stops being a routing problem, and the support team works in one language. ### Document Localization Marketing and product documents need to ship in several languages. The agent runs document translation on each file so the layout is preserved, applies the brand glossary, and returns formatted, translated documents. What used to be a slow round-trip with an external translator becomes a step in the publishing flow, with a reviewer checking the customer-facing copy before it goes live. ### Inbound Message Triage Messages come in across languages and channels. The agent detects and translates each one, then routes it by content. Routine messages are handled automatically in translation. Anything legally sensitive or tied to a large account is flagged and routed to a bilingual reviewer, so machine translation never stands alone on the messages that carry risk. ## Human-in-Loop Highlight Machine translation is excellent and still not something to trust blindly on a contract clause or a customer commitment. When a translation is legally sensitive or customer-facing on a high-value account, FlowRunner routes it through a [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) step: the agent pauses, presents the original and the translation side by side, and sends it to a bilingual reviewer via Slack. They confirm or adjust the wording. Routine translation runs automatically; a person checks the ones where a mistranslation would cost something. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 14 actions ### Translation 1 - **Translate Text** Translates text into a target language using DeepL's neural machine translation. The source language is auto-detected unless specified. ### Writing 1 - **Improve Text** Improves the writing of a text using DeepL Write, fixing grammar, punctuation and phrasing while preserving meaning. ### Documents 3 - **Upload Document** Uploads a document (docx, pptx, xlsx, pdf, srt, txt, html, xlf and more) to DeepL for full-document translation with formatting preserved. - **Get Document Status** Checks the translation status of a previously uploaded document. Returns the status ('queued', 'translating', 'done' or 'error'), the estimated seconds remaining while translating, the billed character count once done, and an error message if the translation failed. - **Download Translated Document** Downloads the translated document once its status is 'done' (check with Get Document Status first), saves it to FlowRunner file storage and returns its URL. ### Glossaries 6 - **Create Glossary** Creates a multilingual glossary (v3) that enforces custom term translations during text and document translation. - **List Glossaries** Lists all glossaries in the DeepL account with their IDs, names, language-pair dictionaries and entry counts. - **Get Glossary** Retrieves the metadata of a glossary by its ID, including its name, language-pair dictionaries, entry counts and creation time. - **Get Glossary Entries** Retrieves the term pairs of one language-pair dictionary in a glossary. Returns both the raw TSV entries as provided by DeepL and a convenient parsed object mapping source terms to target terms. - **Edit Glossary** Updates a glossary (v3): rename it and/or replace the entries of one language-pair dictionary. - **Delete Glossary** Permanently deletes a glossary and all of its language-pair dictionaries by its ID. Returns a deletion confirmation. ### Languages 2 - **List Source Languages** Lists all languages DeepL can translate from, with their language codes and names. - **List Target Languages** Lists all languages DeepL can translate into, with their language codes, names and whether they support the formality option. ### Account 1 - **Get Usage** Retrieves the current billing-period usage of the DeepL account: characters translated so far and the character limit of the plan. ## Frequently Asked Questions ### What can FlowRunner do with DeepL? FlowRunner agents can run Translate Text, Improve Text, and Upload Document in DeepL, plus 11 more actions. ### Does connecting DeepL to FlowRunner require OAuth? No. DeepL connects to FlowRunner with an API key, no OAuth flow required. ### Can DeepL trigger a FlowRunner workflow automatically? DeepL doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at DeepL?** This integration exposes DeepL to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/deepl. Site index: https://flowrunner.ai/llms.txt