- Integrations
- /
- DeepL
- /
- Actions
- /
- Translate Text
ActionDeepLUpdated May 2026
How do I translate text with DeepL?
Short answer: Drop the "DeepL → Translate Text" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Text text | string | Required | The text to translate |
Target Language target_lang | options | Required | Language to translate into |
Source Language source_lang | options | Optional | Language of the input text. Leave empty for auto-detection. |
Formality formality | options | Optional | Controls formality in the translation. Not all languages support this. |
Sample request
{"text": "e.g. Hello, how are you?","target_lang": "{{trigger.target_lang}}","source_lang": "{{trigger.source_lang}}","formality": "{{trigger.formality}}"}
Returns
{"translations": [{"text": "Hallo, wie geht es Ihnen?","detected_source_language": "EN"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Translate Text.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Translate Text.
What does the Translate Text action do in DeepL?
Translates text between languages with optional formality control and HTML/XML tag preservation. DeepL outperforms most alternatives on European-language pairs; the standard hook for production-quality EU-language translation workflows.
What inputs does Translate Text require?
Required: Text, Target Language. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if DeepL returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Translate Text support batch operations?
Yes. Run Translate Text inside a Loop node to process arrays. Tiny Command handles DeepL's rate limits automatically so you don't have to throttle manually.
More actions
Other DeepL actions.
Action
Get DeepL Usage
Returns character_count and character_limit for the current billing period. Pre-flight this on bulk-translation batches to avoid mid-batch quota exhaustion.
ActionList DeepL Languages
Returns supported source and target languages. Useful for dynamically populating language pickers in translation UIs or for validating that requested translation pairs are supported.
Send translate text from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.