Reference · Tools
LingvaNex
Translate text between languages using the LingvaNex Translation API
The LingvaNex node translates text between over a hundred languages, detecting the source automatically unless you specify it, and handling HTML content without mangling the markup. A typical build is translating incoming support messages into the agent's language before they reach the queue.
- Node type
- Action
- Parameters
- 5
- Outputs
- Output, Error
- Credentials
- LingvaNex API
LingvaNex
Translate text between languages using LingvaNex
Overview
LingvaNex is a machine translation API that supports translation between 100+ languages. This tool sends text to the LingvaNex B2B Translation API and returns translated text. It supports auto-detection of the source language, HTML translation mode for preserving markup, and customizable platform identifiers.
Category: Utility
Tool Name: lingvanex
Version: 1
Appearance: Icon: lucide-Languages | Color: #1E88E5
Node Type
Action — processes input items and produces output
Input / Output
| Direction | Port(s) |
|---|---|
| Input | Input |
| Output | Output, Error |
Credentials
This tool requires LingvaNex API credentials. See the Credentials Guide for setup instructions.
Operations
| Operation | Value | Description |
|---|---|---|
| Translate | translate | Translate text to a target language |
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| Text | string | Yes | — | The input text to translate. Supports expressions like {{ $json.body }}. (shown when Operation is translate) |
| Translate To | string | Yes | — | The target language code (e.g., “en_GB”, “fr_FR”, “de_DE”). Use the LingvaNex /getLanguages endpoint or see https://cloud.google.com/translate/docs/languages for language codes. Supports expressions. (shown when Operation is translate) |
| Additional Options | collection | No | {} | Optional settings that customize the translation request. (shown when Operation is translate) |
| — From | string | No | — | The source language code (e.g., “en_GB”, “fr_FR”). If not set, auto-detection is enabled. Supports expressions. |
| — Platform | string | No | api | The platform identifier for the API request. |
| — Translate Mode | string | No | — | Set to “html” to translate and preserve HTML structure. Leave empty for plain text translation. |
| Max Concurrency | number | No | 10 | Maximum number of items to process concurrently. |
Output Data
One output item per input item. The LingvaNex translation response is merged into the item JSON at the top level, so the incoming fields remain addressable alongside the translation result. Binary data is forwarded.
The response body is passed through as the API returns it — the field carrying the translated text is whatever the LingvaNex /translate endpoint names it. Inspect one run’s output to confirm the exact key before wiring downstream expressions.
Usage Examples
- Translate “Hello, world!” to French
- Auto-detect source language and translate to German
- Translate HTML content to Spanish preserving markup
Example Configuration
Translate a field on the item into French, letting LingvaNex detect the source language:
{
"type": "lingvanex",
"parameters": {
"operation": "translate",
"text": "{{ $json.message }}",
"translateTo": "fr_FR"
}
}
State the source language explicitly instead of relying on detection:
{
"type": "lingvanex",
"parameters": {
"operation": "translate",
"text": "{{ $json.message }}",
"translateTo": "de_DE",
"options": {
"from": "en_US"
}
}
}
Translate an HTML fragment and keep its markup intact:
{
"type": "lingvanex",
"parameters": {
"operation": "translate",
"text": "{{ $json.htmlBody }}",
"translateTo": "es_ES",
"options": {
"from": "en_US",
"translateMode": "html"
},
"maxConcurrency": 5
}
}
Error Handling
| Mode | Behavior |
|---|---|
| stop | Halts workflow on first error |
| continue | Skips failed items, passes successful ones through |
| errorPort | Routes failed items to Error output port |
Tips
Translate text between 100+ languages using the LingvaNex machine translation API.
- Language codes are locale-shaped. LingvaNex expects codes like
en_GB,fr_FRandde_DErather than bare two-letter codes. - Leave From empty to auto-detect. Only set it when you already know the source language and want to rule out a misdetection.
- HTML content needs Translate Mode. Without
html, markup in the input is treated as ordinary text. - Options is a collection.
from,platformandtranslateModenest under theoptionskey — they are not top-level parameters.
Frequently asked questions
What format do language codes take?
Locale-shaped codes such as `en_GB`, `fr_FR` and `de_DE` — not bare two-letter codes. A plain `en` will not be accepted.
Do I have to specify the source language?
No. Leave From empty and LingvaNex auto-detects. Set it only when you already know the source and want to rule out a misdetection.
How do I translate HTML without breaking the tags?
Set Translate Mode to `html`. Without it, markup in the input is treated as ordinary text and the tags are translated along with the content.
Where do the optional settings live?
`from`, `platform` and `translateMode` all nest under the Options collection rather than sitting at the top level.
Build with the LingvaNex node
Drop it into a workflow, wire it to an agent, or call it on a schedule. You'll need LingvaNex API credentials first.
Open BusyBotLast updated . Spotted something wrong? Tell us.