Translate
Text → translated languages
Translate uses AI to take the text from an earlier step and rewrite it in the languages you choose, keeping the meaning, names, and numbers intact.
How it works
This node turns one piece of text into as many languages as you need. It reads whatever the step before it produced, an extracted document, a summary, a fetched page, and writes a faithful translation for each language on your list. Meaning, tone, names, and figures carry over; it is not a word-for-word swap.
Each language is a separate pass, so asking for three languages produces three translations. They come back both as one combined text you can hand to a later step and as individual pieces you can reference on their own, so you can email the Spanish version to one recipient and the French version to another.
It runs on the same cheap model by default, with the option to switch to a stronger one when the text is sensitive or full of specialized terms. Because it reads plain text, put it after a step that produces text (Extract, Summarize, Convert) rather than feeding it a raw file.
Common use cases
Real situations where this node earns its place in a flow.
Reach customers in their language
Translate a summary or letter into every language your audience speaks in one step.
Localize documents you generate
Turn an extracted or filled document into another language before it goes out.
Read foreign-language paperwork
Translate an incoming document into your own language so your team can act on it.
Translate in a workflow
A simple example of where this node sits in a flow.
What you set up
- List the languages you want, written any way you like (Spanish, fr, Brazilian Portuguese).
- Leave the model on the cheap default, or switch to the stronger one for sensitive or technical text.
- Optionally cap how long each translation can get.
Common questions
How many languages can I ask for at once?
As many as you list. Each one is translated in its own pass, so the more languages you add, the longer it runs and the more it costs, in direct proportion to the number of languages.
Can I send a specific language to a specific recipient?
Yes. Alongside the combined text, each language is exposed on its own, so a later email or write step can pull just the one you want.
Settings you configure on this node, stored under data.config in the workflow JSON. Leave a field unset to use its default.
languagesreqTarget languages, comma / newline / semicolon separated (free text: 'Spanish', 'fr', 'Simplified Chinese'). One AI pass per language.
Type: stringmodelModel id override (e.g. claude-sonnet-4-6); empty uses the cheap Haiku default.
Type: stringmaxTokensCap on each translation's length in output tokens (max 8192).
Type: numberDefault:4096
How this node appears inside a workflow's nodes[] array (the shape you see in the Developer export / import). A full workflow is { nodes: [...], edges: [...] }.
{
"id": "translate",
"type": "card",
"position": {
"x": 160,
"y": 120
},
"data": {
"type": "translate",
"kind": "processor",
"title": "Translate",
"subtitle": "Text → translated languages",
"config": {
"languages": "",
"model": "",
"maxTokens": "4096"
}
}
}