Set Value With Path

Worth saying up front: this isn't a general-purpose utility you'd reach for in an arbitrary workflow. It's a personal "constants panel" the pack's author built for one of their own video pipelines, and the field labels are written in Vietnamese - a strong sign this node came out of a specific tutorial or course workflow rather than being designed for a general audience.

The mechanics are simple even if the field names need translating. It's five string inputs, and five outputs that mirror them 1:1 - whatever you type into a field comes straight back out the matching output. Here's what each one actually says:

• Tách mask - "split mask" / "extract mask," presumably a label or flag consumed by a mask-extraction step further down the graph.
• Tên file cần lưu - "filename to save."
• Thư mục lưu video kết quả - "folder to save the result video."
• Đường dẫn video gốc - "path to the original/source video."
• License_key - exactly what it says.

Why bundle five unrelated fields into one node instead of scattering separate text nodes across your graph? Convenience, mostly - you set all five values once, up near the top of the workflow, and every downstream node that needs one of them pulls it from here rather than you retyping (or copy-pasting, and inevitably fat-fingering) the same folder path in five different places. It's a legitimate pattern you'll see in other packs under names like "Constants" or "Set" nodes - this one's just scoped narrowly to this author's own pipeline instead of being general-purpose.

The License_key field is the one worth flagging plainly. It sits required, right alongside video-path and save-folder settings, which is the tell that at least part of this pack's functionality is meant to be unlocked with a key issued somewhere else - most likely tied to whatever paid course or template this node family was built for. Nothing in the schema shows what a valid key looks like, or what happens if you leave it blank; that logic lives in the node's Python, not in anything visible from the outside.

Installing it. The pack is comfyui-sortlist by huyl3-cpu, published as comfyui-huyl2-nodes. Search that title in ComfyUI Manager, or clone it directly:

cd ComfyUI/custom_nodes
git clone https://github.com/huyl3-cpu/comfyui-sortlist

Restart ComfyUI afterward.

Troubleshooting. If you picked this node up as part of a shared workflow rather than the author's own course template, the field names alone won't tell you what values belong in them - that's expected, not a defect in the node. The honest move is to leave whatever you don't understand blank, run the workflow, and see which downstream node complains first; that'll tell you which field it actually needed. And if a downstream node behaves as though it never got its input despite this node's outputs looking populated, double-check you haven't mixed up which of the five identically-typed string outputs feeds which wire - with five same-typed outputs stacked together, it's an easy connection to get backwards.