ActionDeepLUpdated September 2026

How do I translate text with DeepL?

Short answer: You can translate text in DeepL by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the DeepL Translate Text action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Translate Text in DeepL — start free All 3 DeepL actions

Translate Text in DeepL — start free

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.

Google Sheets → DeepL

2 Google Sheets triggers

HubSpot → DeepL

18 HubSpot triggers

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 run history shows the failed step with its input and the error message DeepL returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Translate Text support batch operations?

Run Translate Text inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within DeepL's rate limits.

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.

Action

List 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.

Translate Text in DeepL — start free