𝙆 Tencent Translater

This is KayTool's second translation node, and it sits between the other two in how much control it gives you. Like AIO Translater, it uses a hosted backend with no API key for you to manage - the node's own schema description names it as running on the Tencent Translate API specifically, and unlike Baidu Translater, there's no ID/Key field anywhere in this node's inputs, so the credentials clearly live on the author's side, not yours. What it adds over AIO Translater is two text slots instead of one, and an explicit From language picker instead of pure auto-detection.

The two-slot design (Text_A / Text_B in, A / B out) is genuinely handy if you're translating a positive/negative prompt pair, or a title/body pair, and don't want to run two separate translate nodes for what's conceptually one translation job.

How it works

Type or wire text into Text_A and Text_B, pick a From language (or leave it on Auto to detect), pick a To language, and both text slots get translated independently and returned as A and B. The Translate boolean is a straightforward kill switch - flip it off and the node presumably passes text through untranslated, which is a handy way to test the rest of your graph's wiring without burning a translation request on every run while you're still building the workflow.

The inputs and outputs that matter

• Text_A / Text_B (STRING, multiline) - the two texts to translate.
• From (choice of 15: Auto plus 14 languages) - source language, or auto-detect.
• To (choice of 14 languages, default English) - target language.
• Translate (BOOLEAN, default true) - toggle the translation on or off.
• A / B (STRING, outputs) - translated counterparts of Text_A and Text_B.

Installing it

Bundled with the full KayTool pack: ComfyUI Manager → search KayTool → install → restart, or cd ComfyUI/custom_nodes && git clone https://github.com/kk8bit/KayTool and restart. No separate API signup needed for this node specifically.

Common issues

Same underlying risk as AIO Translater: since the credentials and routing are the author's, not yours, a hiccup on that hosted backend (rate limiting, downtime, a changed endpoint) shows up as this node simply failing to translate, with nothing on your end to reconfigure or retry against. If only one of your two text slots is coming back translated, check that both Text_A and Text_B actually have content - an empty slot has nothing to translate and will just come back empty rather than erroring. And if you set From to a specific language but the source text is actually in a different one, you'll get poor or nonsensical results rather than an error - when in doubt, leave From on Auto unless you're certain what language you're feeding in.