📂 IG Folder

IG Folder is the plumbing node that starts most IG workflows. It takes two tiny inputs and turns them into one absolute path string: pick whether you want the ComfyUI input folder or output folder as the parent, type a folder name, and out comes a full filesystem path you can wire into IG Load Images, IG Load Images' explorer friends, or anything else that takes a string path. That's the whole job.

Why does this need to exist? Because several nodes in this pack take forceInput string paths, and typing raw absolute paths into nodes is how you get workflow JSONs that only work on one machine. IG Folder rebuilds the path from ComfyUI's own directories, so a workflow you build here still runs on someone else's install - different ComfyUI/input location, same relative folder name. When you see a shared IG workflow that "just works" for everyone, this node is usually why.

The inputs:

• folder_parent - a dropdown with exactly two options: input folder or output folder.
• folder_name - the subfolder name, as a plain string. Empty is allowed; it just resolves to the parent directory itself.

The single STRING output is the joined absolute path. Note what it doesn't do: it won't browse your disk, and it only knows about those two parents - no arbitrary absolute path, no home-directory shortcut. If you need to point at something outside ComfyUI's input/output roots, you'd skip this node and use a plain string or IG Path Join instead.

It also doesn't create the folder - the Explorer will create its own directories, and Load Images just needs a folder that exists. So if you've wired IG Folder into Load Images and the folder doesn't exist yet, you'll get the loader's FileNotFoundError rather than a folder being made for you.

The install story is the same for every node in this pack:

cd ComfyUI/custom_nodes
git clone https://github.com/IDGallagher/ComfyUI-IG-Nodes
cd ComfyUI-IG-Nodes && pip install -r requirements.txt

Or ComfyUI Manager → search "IG Interpolation Nodes" → Install, then restart. No dependencies beyond the pack's basics, no models, nothing to download. It's a two-line os.path.join with a dropdown, and sometimes that's exactly the right amount of node.