Triple Join Text (Legacy)

Triple Join Text is the most honest node in the pack: its display name ends in "(Legacy)" and the code marks it deprecated. It joins three strings with a separator. That's it. If you've seen a "join text" node in any other utility pack - rgthree, WAS, the hundred others - you already know exactly what this does and whether you need it.

Mechanically it's trivial. Three multiline string inputs (str1, str2, str3), a separator that defaults to ", ", and a boolean add_separator_to_end that appends the separator after the last string when you want a trailing comma. The single str output is just str1 + sep + str2 + sep + str3, with the optional trailing separator on top. separator.join([str1, str2, str3]) in the source, no hidden behavior, no surprises.

So why would you reach for it? The honest answer is that this is the node you'd use to build a prompt from pieces - a base prompt, a style tag, a quality tag - or to assemble a metadata string from components. But it's legacy for a reason: the pack has since moved to more flexible join and text-handling utilities (its text_v3.py module grew a whole family of them), and for anything beyond exactly three inputs you're better off with a node that takes a list. If you're starting a workflow today, a modern multi-input join is the safer habit; this one is only worth wiring up if you're maintaining an old workflow that already uses it, or you genuinely want a dead-simple fixed three-slot join and don't want to think.

One genuine nicety: the inputs are multiline, so each slot can carry a full block of text rather than a single line - and the add_separator_to_end toggle exists specifically for metadata formats that want a trailing delimiter. That's the kind of detail that tells you this node was built to feed Sage Utils' own metadata pipeline, not as a toy.

Install is the pack standard - ComfyUI Manager (search "Sage Utils") or clone:

cd ComfyUI/custom_nodes
git clone https://github.com/arcum42/ComfyUI_SageUtils.git

then restart. Nothing to download beyond the pack; no gotchas specific to this node. If it shows up in your node list greyed or with a legacy banner, that's the deprecation working as intended - it still runs fine, it's just not the recommended path anymore. Use it while you migrate, don't build a career on it.