view_GetWidgetsValues

view_GetWidgetsValues is the node that reads another node's face. Wire any node into its ANY input and it pulls the values of that node's widgets - the settings typed into its on-canvas fields - and exposes them as individual outputs, value_1 through value_20, plus a combined LIST. It's the "give me this node's settings as data" trick that power users rely on, and it saves you from duplicating every parameter twice just so two branches can share one number.

The classic case: you've got a KSampler with a seed widget and a denoise widget, and elsewhere in the graph you want to use those same values - display the seed, feed denoise into a conditional, sync two samplers. The stock ComfyUI way is to convert the node to Primitive and rewire everything, which is invasive and brittle. This node lets you tap the settings without touching the node you're reading. Same for the pack's own controllers: if a stack node holds settings you want to pass somewhere else, read them off here.

How it works

You connect the ANY input to another node in the graph. On each run, the node inspects that source node's widget definitions and current values, then emits them in order on value_1 onward, and the same collection as LIST. value_1 is the first widget, value_2 the second, and so on up to twenty. If the source node has fewer than twenty widgets, the unused outputs simply come out empty.

The inputs and outputs that matter

• ANY - required. Connect the node whose widgets you want to read.
• LIST - all the values as one list, handy for passing the whole set along.
• value_1 … value_20 - individual widget values, one output per widget, in order.

How to install it

Part of the ComfyUI-Apt_Preset pack. Install once via ComfyUI Manager (search "ComfyUI-Apt_Preset") or:

cd ComfyUI/custom_nodes
git clone https://github.com/cardenluo/ComfyUI-Apt_Preset

then run install.bat (Windows) or pip install -r requirements.txt, and restart ComfyUI. No model downloads.

Common issues & troubleshooting

Widget order is the thing to verify first. The node emits widgets in the order ComfyUI lists them, which isn't always the visual top-to-bottom order on the node face. Wire one up, run, and check the LIST against what you see before relying on the individual outputs. Also remember the values are whatever was saved in the workflow at that point - if you change a widget on the source node, queue another run to refresh the outputs.

Two pack-level notes. First, if you're reading a node whose values are computed at runtime rather than typed in, the outputs reflect the last executed values, not live ones. Second, the usual install caveat: niche pack, Bilibili-based author, translated README, and the recurring community report is IMPORT FAILED when dependencies are skipped - run install.bat, restart ComfyUI, and confirm the node loads.