📥 Load Text From Path

The more general sibling of Load Text From Bjornulf Folder. Where that node only ever looks inside ComfyUI/Bjornulf/Text and gives you a dropdown, this one just takes a raw path - anywhere on disk, any filename - and reads whatever text file lives there. Trade a convenient picker for full flexibility.

How it works

Give it a file path, it opens the file, hands back the contents. That's the entire mechanism - no parsing, no formatting, just a plain text read. It's the node you reach for when the text you want isn't sitting in the pack's dedicated snippets folder: a requirements file, a prompt someone else generated, a .txt living in some other project's directory entirely. The README shows exactly this - using it to load a requirements.txt file as an example of pointing it somewhere outside the usual Bjornulf folder structure.

Inputs and outputs

One required input: file_path, a STRING defaulting to Bjornulf/Text/example.txt - that default is a hint, not a requirement; point it wherever you actually need. Notably, you can still point this node at files inside Bjornulf/Text if you want the folder-based files without the dropdown widget - the README calls this out explicitly as a valid way to use it. Outputs mirror the folder-based version: text (contents), filename (just the name, no directory), and full_path (the complete path you gave it, echoed back for downstream use).

Installing it

Bundled with the rest of Bjornulf_custom_nodes. ComfyUI Manager → search the pack title → install → restart, or cd ComfyUI/custom_nodes && git clone https://github.com/justUmen/Bjornulf_custom_nodes and restart manually. No node-specific dependency beyond the pack's base install.

Common issues & troubleshooting

Same path-resolution gotcha that shows up across this pack's file-based nodes: a relative path resolves relative to wherever the ComfyUI process itself is running from, not necessarily relative to your workflow file or your input/ folder. If a path that "should" work errors out with a file-not-found, try an absolute path first to rule that out before you go hunting for other causes.

Because there's no dropdown here - you're typing or wiring a raw string - a typo in the path is the single most common failure. If you're switching between several text files during testing, consider whether the folder-based Load Text From Bjornulf Folder node might actually be the better fit for that specific workflow; it trades flexibility for a dropdown that can't be mistyped. And if the file exists but the node still can't read it, check basic file permissions, especially on a fresh Linux install or a networked/mounted drive where ComfyUI's process might not have read access.