Short answer: You can list deepl languages in DeepL by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the DeepL List DeepL Languages action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Language Type type | options | Optional | Language Type. Options: Source languages, Target languages |
{"type": "{{trigger.type}}"}
[{"name": "English","language": "EN","supports_formality": true},{"name": "German","language": "DE","supports_formality": true}]
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.