TTP_text_mix

Full disclosure up front: this node isn't mentioned anywhere in the pack's README, and it's got essentially no community footprint I could find - so everything here is a straight read of what the node exposes, not a documented workflow. Worth writing up anyway, because the shape of it is genuinely useful if it does what it looks like it does.

What it looks like it's for. Four multiline text inputs: text1, text2, text3, and template, all empty strings by default. Four outputs: text1, text2, text3 (passed straight through unchanged) and final_text. The obvious reading is a prompt-templating helper - you keep a reusable template string in one place, and text1/text2/text3 are separate snippets (say, a subject description, a style tag, a lighting note) that come from three different upstream sources in your graph, getting combined into final_text according to whatever the template says.

Why that pattern is genuinely handy, if it works as it looks. If you've ever built a prompt out of four or five string-concatenate nodes chained together, you know how quickly that gets messy to read and edit. A single node that holds the assembly template in one visible place, with the three inputs staying available as their own outputs (so you're not forced to also wire a separate pass-through if you need one of the raw snippets somewhere else too), is a reasonable answer to that mess.

What I can't tell you. The exact placeholder syntax the template field expects - whether it's something like {text1}, %text1%, or positional - isn't documented in the README or anywhere else I could verify, and I'm not going to guess at syntax and present it as fact. If you're going to use this node, the honest approach is: put an obvious literal word in text1 (something you'd immediately recognize in the output), write a template that you'd expect to substitute it, and check final_text before you build anything that depends on it working a specific way.

Install. ComfyUI Manager, search "Comfyui_TTP_Toolset", or cd ComfyUI/custom_nodes && git clone https://github.com/TTPlanetPig/Comfyui_TTP_Toolset, then restart. It's a text-only node - no models, no extra dependencies.

Common issues. Given the total absence of documentation and community discussion for this specific node, I don't have real, sourced failure modes to report - and I'd rather leave that section honestly empty than invent plausible-sounding bugs. The one practical piece of advice: test it in isolation first. Wire text1, text2, text3, and template directly into Show Text nodes (or just eyeball final_text) before you build a prompt pipeline that depends on this node's exact templating behavior, since there's no public reference to fall back on if it doesn't do what you expect.