Get Glossary Entries
deepl.get_glossary_entries
ActionAI & modelsconnection required
Calls the DeepL API with the connection's credentials.
Fetch the term pairs a glossary holds, as a source-to-target mapping.
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, 1 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 |
|---|---|---|---|---|---|
glossary_id Identifier of the glossary to act on, as returned by deepl.list_glossaries. | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
glossary_id Identifier of the glossary that was read. | string | — |
entries The term pairs, keyed by source term with the target term as the value. | object | — |
count How many term pairs the glossary holds. | number | — |
tsv The raw tab-separated body DeepL returned, for round-tripping into deepl.create_glossary. | string | — |
{
"count": 0,
"entries": {},
"glossary_id": "",
"tsv": ""
}See Get Glossary Entries 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.