From List Type Node

Honest first sentence: this node is deprecated, and the pack's own code says so - its display name is literally FromListTypeNodeDEPRECATED(batch). I'm writing about it because you will meet it in older workflows, and knowing what it is beats staring at an error message.

From List Type Node converts a Python list into a tuple, set, dict, or dict-from-pairs. It sits in the ovum/lists/any category of the comfy-ovum pack, and it's a direct descendant of aria1th/ComfyUI-LogicUtils' pystructure code - the source file is upfront that it was "stolen from/extends functionality of" that excellent logic pack, which is a recurring theme in comfy-ovum. When the author reorganized the pack, this older converter was kept around for compatibility while two newer variants took over its job.

What it does (so you can recognize it)

Inputs: py_list (LIST) and target_type - list, tuple, set, dict, or dict_pairs.

• tuple → (a, b, c, ...)
• set → deduplicated
• dict → index→value, [a, b, c] becomes {0: a, 1: b, 2: c}
• dict_pairs → expects [key, value] pairs, builds a real keyed dict

Output: a single * socket. The batch-style naming means it was designed to sit in ComfyUI's batch/list region of the graph.

The honest recommendation: use its replacements

Ovum now ships the same conversion twice more, in cleaner homes:

• From List Type Node Ovum (ovum/lists/python) - the plain-Python-list version
• From Batch Type Node Ovum (ovum/lists/comfy) - the batch-flavored version

Both implement the identical conversion logic without the DEPRECATED flag. When you find From List Type Node in a shared workflow, your move is usually: swap it for the matching non-deprecated variant. Nothing else in the graph needs to change - same inputs, same output shape.

Installing it

It's part of sfinktah/comfy-ovum:

cd ComfyUI/custom_nodes
git clone https://github.com/sfinktah/comfy-ovum

or search comfy-ovum in ComfyUI Manager, then restart.

Gotchas

Don't reach for this node in new work. If an old workflow loads it and behaves fine, leave it alone - it still functions. If you're editing that workflow anyway, take the ten seconds to swap in the current variant so you're not carrying a deprecated node forward. And if dict_pairs throws, check that every element is a proper two-item pair; that's the one place the conversion is strict. This is a "know it so you can move past it" node, not a "start here" one.