📂 IG Path Join

IG Path Join does one thing: it takes two strings and joins them into a path with os.path.join. That's the entire node - two inputs, one output, no settings. It exists because building paths by string concatenation is how you get C:\foo\bar\baz vs /foo/bar/baz disasters when a workflow moves between Windows and Linux machines. os.path.join handles the separator for you, which is exactly what you want in a path you're going to hand to a node that opens files.

It's the natural partner to IG Folder: Folder gives you a ComfyUI input/output root, Path Join lets you append the rest of the path in a second step, and the whole thing stays portable. It also works as a generic string-combiner if that's what your workflow needs - nothing here is path-aware beyond the join itself, so it won't catch mistakes like doubling slashes or trimming spaces.

Inputs and output are minimal:

• first - STRING (default empty, single-line).
• second - STRING (default empty, single-line).
• Output: STRING, the joined result.

One honest note: because ComfyUI passes empty defaults, feeding it an empty first returns just second - which is fine, but means there's no validation to stop you from building a broken path. The node trusts you. If you're assembling a path that must exist, wire it into IG Load Image or Load Images and let their error messages tell you whether you got it right.

Install is the pack standard - Manager → search "IG Interpolation Nodes" → Install, restart, or:

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

This is a genuinely thin utility node, so there's no troubleshooting section worth inventing. If the path it produces doesn't work, the bug is upstream of the node - check what strings you're feeding it. The README is :), but this one's behavior is a single line of os.path.join in nodes/io.py, so there's not much to misread.