Nodes/SP-Nodes/SP_UnlistValues
ComfyUI Node

SP_UnlistValues

One of SP-Nodes' rougher, unlabeled corners

By bananasss00·Created 2 years ago·Updated 6 days ago· 20
SP_UnlistValues
  • value
  • *

Worth flagging up front: this node's own category path ends in Tmp. Combined with SP_Pass living under _test_, that's the second signal in this pack that not every node here is meant as a finished, documented feature - some are the author's own working scraps, shared because the rest of the pack was already public. Take the description below as a reasonable reading of what the schema shows, not a confirmed account of intended behavior, and test it yourself before building anything load-bearing on top of it.

What the schema tells us

SP_UnlistValues takes one required input, value, typed "any," and produces one output, also "any," not marked as a list. That's the entire interface - no other settings, no tooltip, nothing else to configure.

Several other nodes in this pack - SP_XYValues, StrToCombo - build list-typed outputs from a block of text, ready to feed ComfyUI's native list-execution behavior (where a downstream section of the graph runs once per item in a connected list). SP_UnlistValues sits logically on the other side of that: something that takes a list-shaped connection and hands back a single, non-list value, most plausibly by unwrapping it so a node further downstream that expects one plain value instead of a list has something it can actually use. The name supports that reading directly - "unlist" as the inverse of turning something into a list.

Practical guidance

Given the ambiguity, the honest advice is: reach for this node only if you already understand ComfyUI's list-execution model well enough to test its behavior against your own expectations before relying on it. If you're trying to solve "I have a list but this node wants a single value," it's worth trying - but confirm the actual output with a Preview or Display node before wiring it into anything that matters. If it doesn't do what you expect, you're not missing something obvious; this corner of the pack just isn't documented, and the category name is telling you that plainly.

Installing it

Ships with the SP-Nodes pack, same install as everything else in it:

  • ComfyUI Manager: search "SP-Nodes", install, restart.
  • Manual: cd ComfyUI/custom_nodes && git clone https://github.com/bananasss00/ComfyUI-SP-Nodes, restart ComfyUI.

No models or extra dependencies - whatever it does, it does it in plain Python with no external requirements.

Troubleshooting

There's no community discussion of this specific node to draw real failure reports from, and given the Tmp category, that's not surprising - it likely doesn't see much use outside the author's own workflows. If it behaves unexpectedly, the most useful thing you can do is exactly what's suggested above: isolate it with a Display or Preview node on both sides and confirm what actually goes in versus what comes out, rather than assuming the documented-sounding name tells you the whole story.

CategorySP-Nodes/Group Nodes/Tmp

Inputs (1)

NameTypeDefaultDescription
value*

Outputs (1)

NameTypeDescription
**