TOO Preset Text 📋

TOO Preset Text is a dropdown that spits out a saved string. Pick a preset, out comes text. It's the definition of a plumbing node - one input, one output, nothing to tune - but the twist is where the presets live and how you edit them.

The presets are stored in a JSON file inside the pack (presets/text_presets.json), and the node comes with four to start: default negative ("worst quality, low quality, jpeg artifacts"), remove (a \b pattern), regex : extract filename from, and japanese woman. The last one's value is a Chinese-language prompt, which is a good reminder this pack was built by one person for their own workflow - you're expected to replace these with yours.

Why use a preset node at all when a plain string node works? Because the pack exposes two HTTP routes on the ComfyUI server (/too/presets/list and /too/presets/save) that a small dialog in the node's UI uses. So you edit presets from inside ComfyUI - add one, rename it, change its text - without ever opening a file editor. It's the "one authoritative source, many consumers" value-node pattern from the KB's plumbing essay, applied to reusable text: define your negative prompt once, reference it everywhere, fix it in one place.

Inputs and outputs. One required input, preset - the dropdown, populated from the JSON file at node-creation time. One output, text (STRING). If you add a new preset while ComfyUI is running, refresh the page so the dropdown rebuilds.

Install.

cd ComfyUI/custom_nodes
git clone https://github.com/tetsuoo-online/Comfyui-TOO-Pack

or ComfyUI Manager → "Comfyui-TOO-Pack" → restart.

Gotchas. The dropdown options are baked in when the node is created, so editing the JSON on disk (or via the dialog) needs a page refresh before new presets appear. Also, the included presets are a mixed bag - two of them are regex fragments, and this node just returns text; it doesn't apply regex for you. If your preset is \b, that's literally what you get out. That makes more sense when you use this node to feed a node that does understand regex (or when you just want raw snippets to paste around). It's a tiny convenience node, but once you've got your five standard strings in it, you'll miss it when you use a stock workflow that makes you retype them.