CRZ Dashboard Node

CRZ Dashboard Node is the pack's ambitious experiment: one node that's supposed to figure out what you're connecting it to and turn itself into the right control automatically. Plug it into a boolean input and it becomes a toggle. Plug it into a number and it becomes a slider. Drop a dropdown list on it and it becomes a dropdown. That's the dream, anyway - the author's own README section for it is titled "Experimental," and it's worth reading that framing before you build a workflow around it.

This is from ComfyUI-CRZnodes, CoreyCorza's dashboard pack. In the launch thread the author was open about the trade-offs: the node is meant to be an "all-in-one replacement for the other individual dashboard nodes," but it was never heavily tested, and - this is the honest part - the author doesn't want to break their old workflows, so the individual nodes keep doing their own thing while this one goes its separate way. You're basically being offered a beta in the README of a small pack. That's rare in this ecosystem and worth appreciating.

How it works

The Python side is deliberately loose: a hidden slider widget (FLOAT, default 0.0), and a main() that "smart-converts" the value - whole floats become ints, non-whole floats stay floats, strings pass through. The frontend then adapts the drawing based on the slider_type property: FLOAT, INT, BOOLEAN, or COMBO. The output is typed * (any) so ComfyUI lets you plug it into anything.

In practice the "auto-detect what it's connected to" part is more aspiration than reliable behavior. The frontend reads a saved slider_type and draws accordingly, but the automatic detection of what the downstream socket wants is exactly the part the author says isn't done well. You can still force it: set the type in the node's properties.

Inputs and outputs

• No required or optional inputs - the configuration lives in hidden widgets.
• * (output) - the current value, type-converted as best it can.

That's it. One node, one output, a whole pile of hidden state.

Should you use it?

Here's my take, and it's the same take the README implies: use the individual nodes instead. The dedicated CRZ Boolean Toggle, Float Slider, Integer Slider, Custom Dropdown, and the auto-inheriting CRZ Dropdown are each simpler, each tested more, and each have clearer configuration (double-click to set range/options). The Dashboard Node is the one you try because it's neat, hit the "it didn't guess what I wanted" wall on, and then quietly swap back.

The exception: if you're building a workflow where the type of a control genuinely needs to change at runtime, or you want a single node whose display you control via properties, this is the only one that tries. Just be ready for surprises, and don't share a workflow built on it without testing every type mode yourself.

Installing it

Same as the rest of the pack: ComfyUI Manager → search ComfyUI-CRZnodes → install → restart. No requirements, no models.

cd ComfyUI/custom_nodes
git clone https://github.com/CoreyCorza/ComfyUI-CRZnodes.git

The trap to avoid

Because it outputs * (any), ComfyUI won't stop you from wiring it into anything - which means type mismatches surface as weird behavior downstream instead of a clear "can't connect" error. If a workflow that uses this node produces nonsense, check what type the node actually emitted (FLOAT vs INT vs BOOLEAN) before debugging the rest of the graph. That one habit will save you most of the pain this node can cause.