DeepL

undefined

Detail	Value
Category	AI
Base URL	https://api-free.deepl.com/v2
Authentication	API Key
Endpoints	5
Connector key	deepl

Using DeepL in a workflow

1. Go to Connections and click New Connection.
2. Pick DeepL from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET	Translate
GET	Documents
GET	Languages
GET	Glossaries
GET	Usage

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET

Translate

Detail	Value
Operation ID	translate_0
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your DeepL connection from the Connection dropdown.
3. In the Operation dropdown, select translate_0.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream DeepL API reference.

GET

Documents

Detail	Value
Operation ID	documents_1
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your DeepL connection from the Connection dropdown.
3. In the Operation dropdown, select documents_1.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream DeepL API reference.

GET

Languages

Detail	Value
Operation ID	languages_2
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your DeepL connection from the Connection dropdown.
3. In the Operation dropdown, select languages_2.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream DeepL API reference.

GET

Glossaries

Detail	Value
Operation ID	glossaries_3
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your DeepL connection from the Connection dropdown.
3. In the Operation dropdown, select glossaries_3.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream DeepL API reference.

GET

Usage

Detail	Value
Operation ID	usage_4
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your DeepL connection from the Connection dropdown.
3. In the Operation dropdown, select usage_4.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream DeepL API reference.