Nodes/WGC Nodes/Unpack Text 3
ComfyUI Node

Unpack Text 3

The outputs that name themselves

By heyheywoah·Created about a month ago·Updated about a month ago· 1
Unpack Text 3
  • bundle
  • text_01
  • text_02
  • text_03

The whole gimmick of WGC-Nodes lives in this tiny node. Unpack Text 3 takes a WGC_TEXT_BUNDLE in and gives you three STRING outputs, then quietly renames those outputs to match whatever labels the upstream Pack Text node is using. Wire a Pack Text 3 whose boxes are called positive, negative, quality into this, and you get three outputs literally named positive, negative, quality. No legend needed.

It's the return half of a pack/unpack pair. Pack Text carries a bunch of strings down one clean connection; Unpack Text turns them back into individual wires where your workflow actually uses them - a CLIP Text Encode, a prompt builder, a LoRA stack, anywhere that eats a STRING.

How it works

The bundle is just a tuple of strings. This node reads positions 0 through 2 and emits them as three STRING outputs (text_01, text_02, text_03). The rename magic is frontend: the editor walks the wire back to the connected Pack node - following ordinary Reroute nodes as it goes - to discover the display labels. It's cosmetic, but it's the cosmetic that keeps a graph readable without a sea of text_01s.

Label modes

Three modes on the node's UI:

  • Live - follow the Pack labels automatically. Default, and usually what you want.
  • Frozen - keep the current labels until you press Refresh Labels. Handy when you don't want outputs re-labeling themselves mid-edit.
  • Manual - turn auto-renaming off entirely and edit the output names by hand.

Inputs and output

  • bundle (input) - the one connection, WGC_TEXT_BUNDLE from any Pack Text size.
  • text_01, text_02, text_03 (outputs) - the three STRINGs.

Sizes are forgiving. Feed it a Pack Text 5 and it just takes the first three, dropping the rest; feed it a bundle with only two strings and the third output comes back as an empty string, which is perfect for optional conditioners that tolerate blanks.

Install

The pack is heyheywoah/WGC-Nodes - installing it gets you all ten nodes. ComfyUI Manager → search "WGC Nodes", or:

cd ComfyUI/custom_nodes
git clone https://github.com/heyheywoah/WGC-Nodes.git

Restart ComfyUI. No dependencies, no models, no API key.

Where people get tripped up

  • Labels didn't update. If you renamed a box on the Pack side and the output name didn't follow, hit Refresh Labels, or check the label mode isn't Frozen/Manual.
  • Subgraph boundaries. Label discovery across a collapsed Subgraph region isn't guaranteed in the 0.1.0 release - the strings still flow correctly, only the auto-naming can miss. Use Frozen or Manual there.
  • Empty output you didn't expect usually means the upstream bundle had fewer strings than this node expects. That's by design, not a bug.

Three outputs isn't much, but it's the cleanest possible demonstration of the pack's trick: labels that stay out of the payload and come back automatically.

CategoryWGC/Text

Inputs (1)

NameTypeDefaultDescription
bundleWGC_TEXT_BUNDLE

Outputs (3)

NameTypeDescription
text_01STRING
text_02STRING
text_03STRING