Short answer: Drop the "DeepL → Translate Text" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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. |
{"text": "e.g. Hello, how are you?","target_lang": "{{trigger.target_lang}}","source_lang": "{{trigger.source_lang}}","formality": "{{trigger.formality}}"}
{"translations": [{"text": "Hallo, wie geht es Ihnen?","detected_source_language": "EN"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.