📁 NL Project Path

Every studio pipeline eventually dies the same death: someone hardcoded a path, the project moved, and now nothing resolves. NL Project Path is this pack's small insurance policy against that. It reads the project path from the NL Workflow context panel and hands it to your graph as a string, so your read and write nodes build their paths from context instead of carrying absolute paths around.

No inputs, one output: project_path, a STRING. That's the whole node. You wire it into path construction - typically by concatenating it with your shot/folder names before it reaches NL Read or NL Write - and the actual location of the project lives in one place: the NL Workflow panel. Move the project, update the panel, and every node that references it follows along.

This becomes genuinely powerful when you combine it with the pack's template and subgraph sharing. The README describes how shared templates get their network paths normalized per host (\\server\... on Windows vs /mnt/server/... on Linux). A workflow that reads its project root from NL Project Path instead of a typed-in Z:\projects\... is a workflow you can hand to a colleague on the other OS and have it just work.

When it's worth it vs. when it's ceremony

For a hobbyist generating single images, this node is a no-op. You have one folder; type the path. It earns its keep the moment you have any of: multiple projects, a shared drive, templates you reuse, or another person who needs to run your workflow. If you've ever inherited a ComfyUI workflow from the community and spent an hour fixing broken absolute paths, you already know the failure mode this prevents. The ecosystem's "why does no workflow I download work" complaint is mostly this problem wearing a different name.

Install

Standard pack install:

cd ComfyUI/custom_nodes
git clone https://github.com/NOLABEL-VFX/ComfyUI-NL_Nodes

or ComfyUI Manager → search "ComfyUI-NL_Nodes", then restart. The README's own quick start is a good model for the whole system: open NL Workflow, fill in project/scene/shot and the project path, hit Apply, and then let nodes like this one read from it. Like its siblings in the Workflow category, this node returns nothing meaningful until you've actually applied a context - the panel is the source of truth, not the node.