Route by Language
Branches the conversation based on the current active language, enabling language-specific flows and content.
The Route by Language node branches the conversation based on the virtual being's current active language. Use it to deliver language-specific content, route to language-specific flows, or apply different logic depending on which language the user is conversing in.
Available in: Handlers, custom Conversational Flows and Automations.
Configuration
The node generates one output port per configured language branch, plus a default port for any language not explicitly handled.
Adding Language Branches
Click + Add case to add a new language branch. For each branch, select the language code from the dropdown (e.g., en-US, pl-PL, de-DE).
Connect each port to the appropriate next node for that language.
Typical Patterns
Language-Specific Flow Routing
Route by Language
├── en-US ──► Go to Flow (EnglishMain)
├── pl-PL ──► Go to Flow (PolishMain)
└── default ──► Go to Flow (EnglishMain)Language-Specific Text Response
Route by Language
├── en-US ──► Text ("How can I help you?")
├── pl-PL ──► Text ("W czym mogę pomóc?")
└── default ──► Text ("How can I help you?")Active Language vs. Detected Language
Route by Language branches on the currently active language – the language the virtual being is currently operating in. In the On Language Change handler, this is the language before the pending change (the new language hasn't been applied yet).
Use Accept Language Change before Route by Language if you need to branch on the newly accepted language rather than the previous one.
Is Flow Active
Checks whether a specific Conversational Flow is currently in the flow stack, enabling guard logic to prevent flows from being re-triggered.
Route by Profile
Branch the conversation based on which Profile is running the pipeline. Useful for shared flows that need touchpoint-specific logic.