ToColorList

ToColorList is the color member of the bmad "make a list" family: it takes several individual COLOR inputs and bundles them into a single Python list. The COLOR type is the pack's own way of carrying a color value around (produced by the Color (RGB) node or Color (RGB from Hex)), and when you've got a palette's worth of them that need to travel together, this is the collection point.

The input that matters

inputs_len - the number of input sockets (default 2, up to 32). Set it to 3 and you get color_0, color_1, color_2. Output: a single COLOR list. Match the count to the colors you actually wire in; empty slots become empty entries.

Why you'd reach for it

Palette workflows. If you're building a color scheme - from a FindComplementaryColor output, hand-picked RGB values, or sampled colors - and you want to feed the whole set to a node that consumes a list of colors, this is the glue. It also round-trips with the family's splitters (FromListGetColors / FromListGet1Color), so you can swap between "one wire per color" and "a list of colors" without rebuilding the graph. The bmad pack treats color as a first-class datatype in its HSV/color-analysis nodes, and ToColorList is how multiple colors stay organized.

Installing

Ships in comfyui_bmad_nodes, bmad4ever's grab-bag of API, CV, and utility nodes. ComfyUI Manager - search "comfyui_bmad_nodes" (or "Bmad Nodes") - install, restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/bmad4ever/comfyui_bmad_nodes
cd comfyui_bmad_nodes
pip install -r requirements.txt

Restart after. No model downloads; pure Python with no extra dependencies for the list node itself (the color pipeline around it lives in the CV half, so keep opencv installed if you're using RGB to HSV and friends).

A niche member of a niche family, sure - but if you do palette work in this pack, you'll want it. It's the only one that bundles the pack's custom COLOR type, so there's no core-ComfyUI equivalent to fall back on.