Detect Language
lingvanex.detect_language
ActionBusiness appsconnection required
Calls the Lingvanex API with the connection's credentials.
Detect which language a piece of text is written in.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Lingvanex
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- base_url, compat_base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 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 |
|---|---|---|---|---|---|
text The text to send, as a single string. Use 'texts' instead to send several strings in one call. | string | No | — | — | Hello, world! |
texts Several strings to send in one call, as a JSON array. When it is set it replaces 'text' and the response carries one entry per string. | array | No | — | ≥ 1 characters; array of string | ["Hello, world!","Good morning"] |
- At least one of text, texts must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"text": "Hello, world!",
"texts": [
"Hello, world!",
"Good morning"
]
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
language The first language code Lingvanex detected. | string | — |
detections Lingvanex's own detection list, as returned. | array | — |
count How many detection entries came back. | number | — |
{
"count": 0,
"detections": [],
"language": ""
}Related Lingvanex nodes
See Detect Language run in a workflow.
In a technical demo we add the Lingvanex connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.