Skip to content
For LLMsView as Markdown·

Google Cloud Translation

undefined

DetailValue
CategoryAI
Base URLhttps://translation.googleapis.com/v3
AuthenticationSee connector docs
Endpoints5
Connector keygoogle-translate

Using Google Cloud Translation in a workflow

  1. Go to Connections and click New Connection.
  2. Pick Google Cloud Translation 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

EndpointSummary
GET Translate Text
GET Detect Language
GET Supported Languages
GET Glossaries
GET Batch Translate

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

GET

Translate Text

DetailValue
Operation IDtranslate_text_0
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Google Cloud Translation connection from the Connection dropdown.
  3. In the Operation dropdown, select translate_text_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 Google Cloud Translation API reference.

GET

Detect Language

DetailValue
Operation IDdetect_language_1
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Google Cloud Translation connection from the Connection dropdown.
  3. In the Operation dropdown, select detect_language_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 Google Cloud Translation API reference.

GET

Supported Languages

DetailValue
Operation IDsupported_languages_2
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Google Cloud Translation connection from the Connection dropdown.
  3. In the Operation dropdown, select supported_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 Google Cloud Translation API reference.

GET

Glossaries

DetailValue
Operation IDglossaries_3
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Google Cloud Translation 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 Google Cloud Translation API reference.

GET

Batch Translate

DetailValue
Operation IDbatch_translate_4
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Google Cloud Translation connection from the Connection dropdown.
  3. In the Operation dropdown, select batch_translate_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 Google Cloud Translation API reference.