🔧 CR String To Combo

A lot of ComfyUI nodes take their options from a dropdown - a sampler_name on a KSampler, a checkpoint file, a resize method - and that dropdown is a fixed-choice type, not a plain string socket. You can't normally wire text into it. CR String To Combo exists for the moment you need to: you've got a value coming out of a text pipeline (an API parameter, a value assembled by another Comfyroll text node, something read from a file) and you need it to land in a socket that expects one of those combo-style choices.

How it works

There isn't much to the mechanism - it takes a text string and passes it out typed as *, ComfyUI's wildcard type, which is loose enough to connect into sockets that a strict STRING output sometimes can't. What actually matters is what happens on the other end of that wire: this node doesn't validate or coerce your text against the target combo's list of valid options. It just forwards whatever string you typed. If the receiving node's combo doesn't recognize that exact value, the run fails - a real, documented pain point people run into trying to drive a sampler's sampler_name from an external text variable, where the fix is making sure the string matches one of the sampler's actual option names character-for-character, not a close approximation.

So the workflow is: open the target node normally once, note the exact spelling of the option you want (case, spacing, underscores - all of it), then type that exact string into CR String To Combo instead of hand-guessing.

The inputs and outputs that matter

• text - the string you want interpreted as a combo selection. No default; you type this yourself.

Output: a single any slot (wildcard * type) carrying that string forward, plus the standard show_help link.

How to install it

ComfyUI Manager - search "Comfyroll Studio", install, restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/Suzie1/ComfyUI_Comfyroll_CustomNodes.git

then restart. No models, no dependencies.

Common issues

The run fails with an unclear error the moment it hits the receiving node. This is almost always a text mismatch - your string doesn't exactly match one of the target combo's valid values. Go open that node's dropdown directly and copy the option text verbatim rather than typing it from memory; sampler and scheduler names in particular are full of easy-to-miss underscores and casing (dpmpp_2m vs DPM++ 2M, say).

It "works" but the wrong option gets selected. Trailing whitespace is a quiet culprit here too - if your text came out of another string node (CR Split String, for instance) it may be carrying a leading or trailing space that looks invisible in a preview but doesn't match the combo's exact string.

No Comfyroll nodes appear at all. That's the pack failing to load, not this node in particular - check your ComfyUI console for Comfyroll Studio: Failed to load ... nodes, most often caused by a Pillow version conflict introduced by another custom node pack, and reinstall Pillow or update Comfyroll through Manager to fix it.