List Supported Languages
deepl.list_languages
ActionAI & modelsconnection required
Calls the DeepL API with the connection's credentials.
List the languages DeepL can translate from, or the languages it can translate into together with their formality support.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- DeepL
- Secret shape
- the DeepL auth key, or {"api_key": "…"}
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
language_type Whether to list the languages DeepL accepts as input or the languages it can produce. Only target entries carry supports_formality. | string | No | source | one of "source", "target" | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"language_type": "source"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
languages[].language The DeepL language code, such as DE. | string | — |
languages[].name The language's English name. | string | — |
languages[].supports_formality Whether formality may be set for this language; target entries only. | boolean | — |
count How many languages came back. | number | — |
type Which list was requested: source or target. | string | — |
{
"count": 0,
"languages": [
{
"language": "",
"name": "",
"supports_formality": false
}
],
"type": ""
}See List Supported Languages run in a workflow.
In a technical demo we add the DeepL connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.