Collect Files

Full disclosure before anything else: this is the least-documented node in the whole pack. No description, no tooltips on any field, and it's not one of the nodes the README covers - only the video-segmenting node gets that treatment. So what follows is a read of what the field names and defaults point to, not a description pulled from author documentation, and I'm flagging that distinction clearly rather than presenting a guess as fact.

What it looks like it's for. The field names line up pretty clearly around one job: pull matching file paths out of a block of text and land the results in a destination folder. text is a multiline field - the kind of thing you'd feed a directory listing, a log, or output from an upstream "Show Text"-style node into. pattern (default .mp4) is what a path has to match to get picked up - the default alone tells you this was built with video files specifically in mind. exclude lets you carve out matches you don't want swept in. dest_folder defaults to /content/ComfyUI/output/I2V, another Colab-flavored path (the /content/... prefix is Google Colab's standard mount point) that's clearly aimed at an image-to-video pipeline specifically. The single output, result, is a string - presumably either a status message or a list of what got collected, but the schema doesn't say which, so the honest answer is: check it in the UI the first time you run this, don't assume.

Inputs and outputs, for reference. Required: text (multiline string), pattern (string, default .mp4), exclude (string, default empty), dest_folder (string, default /content/ComfyUI/output/I2V). Output: result (string).

Because none of this is documented anywhere in the pack, the sensible move is to test it on a small, disposable block of text before trusting it inside a real pipeline - you want to see what result actually contains and confirm pattern behaves the way you expect before it's doing something you can't easily undo (moving or collecting real output files).

Installing it. Same pack as everything else here - search comfyui-huyl2-nodes in ComfyUI Manager, or:

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

Restart ComfyUI.

Troubleshooting. Given there's no ground truth beyond the field names, the one honest note here is this: if result comes back empty or clearly wrong, check first that text actually contains something pattern can match as a literal substring. Nothing in the schema suggests glob or regex support - no wildcard syntax hinted at anywhere - so until proven otherwise, treat pattern as a plain substring match rather than something more clever.