LingvaNex n8n integrationAutomate LingvaNex with n8n.

The move worth remembering is that placement. Put the LingvaNex node after the node that brings the text in, and before the node that sends it out. In the Text field you write an expression, the n8n way of pointing at a value from the item that just arrived, in the form {{ $json.field }}. In Translate To you set the language you want out. That is the whole wiring, and everything below is a variation on it.

First variation: inbound messages the team can read. A support email lands in Gmail, the LingvaNex node translates the body, and the translated version goes into the Slack channel where the team already works. Nobody switches to a browser tab to find out what a customer asked.

Second variation: content you publish twice. A list of product descriptions sits in Google Sheets, one row per item. The workflow reads a row, translates the description, writes it back or drops it into a Google Docs file for a human to review. Because From is optional, mixed-language source rows still work: leave it empty and auto-detect mode handles them.

Third variation: text that carries markup. A newsletter body or a help article is rarely plain text. Set Translate Mode to html and the structure is preserved through the translation instead of coming back as a flattened block. It is the one option people find too late, usually after pasting a broken layout into a CMS.

Two things to know before you build. LingvaNex has no trigger node in n8n, so a workflow that uses it starts from a Schedule Trigger at a fixed interval, from an n8n Webhook, meaning a URL a third-party service calls, or from the trigger of another tool. And for any LingvaNex API endpoint outside this node, the HTTP Request node calls it directly and reuses the same credential through predefined authentication. If you are still deciding whether n8n is the right home for this, the n8n review goes through it in detail.