Blender Input Combo Box

Sometimes the user of your workflow shouldn't be allowed to type anything - they should pick. BlenderInputCombo is the dropdown (combo box) that ComfyUI-Blender renders on its Blender panel: you define the list of choices once, and the person at the panel picks one. Style presets, aspect ratios, which character's look to apply, which texture set to load - anything with a bounded set of options is a combo box, not a text field. It's the input node that turns a workflow into something you'd feel okay handing to someone who's never opened ComfyUI.

Mechanically it subclasses ComfyUI's built-in String primitive and outputs the chosen value as a string. In a ComfyUI-only graph it's just a string with an opinionated set of widgets; the real behavior shows up in the Blender add-on, which renders the dropdown from your list.

Inputs and outputs

• value - the selected item, as a string. Whatever the dropdown currently holds is what flows downstream.
• list - the whole point. A multiline field, one option per line, that becomes the dropdown's choices in Blender. Set it to Style A\nStyle B\nStyle C and you get a three-option dropdown.
• default - which item the dropdown starts on. Needs to match a line in list exactly (case-sensitive), or the box will start empty and confused.
• format_path - if your choices are file paths, this normalizes the selection to the OS where ComfyUI runs. Handy when the pick list is "which texture file" and Blender lives on a different OS than the server.
• order - panel position, lower first.

Optional group input for nesting inside a Blender Input Group box. Output is a single COMBO - an any-type socket, so it'll wire into string, enum, or even model-name inputs without a fight.

Installing it

Whole-pack routine. ComfyUI side, ComfyUI Manager → search "ComfyUI-Blender", or:

cd ComfyUI/custom_nodes
git clone https://github.com/alexisrolland/ComfyUI-Blender

Restart ComfyUI. No extra Python dependencies, but you need a current ComfyUI - schema v3 custom nodes, and the README is explicit that old builds won't load them. The Blender add-on is the other half: a ZIP from the latest release installed via Edit > Preferences > Add-ons > Install from Disk.

Where people get burned

The drop-down only exists after an API-format export and import into the add-on, and the classic failure is a default that doesn't exactly match a line in list - the add-on renders the list but can't select your default, leaving the box blank. Trailing spaces in either field cause this too, and it's maddening until you notice. Keep the list values short and clean; long strings make the dropdown wider than you want on a Blender panel. And as always: the node title is the label, so "Style Preset" beats "combo1". VRAM is shared with the viewport when both run on one GPU, though a dropdown is about the cheapest control this pack can draw.