Load Text File (Simple) v7.0 - Akki

The Load Text File (Simple) v7.0 is the least exciting node in the AkkiNodes pack, and that's a compliment. It reads a text file from disk and hands you its contents as a string. No dropdowns, no dynamic UI, no JavaScript. One path in, one string out. It's the node you use when you just want your story, screenplay, or bible in the graph and you can't be bothered with ceremony.

It's the perfect first node for testing the AkkiNodes suite on its own: you don't need a full pipeline to see whether the LLM Loader is working, because this node is just file reading. Load a saved screenplay into it, wire the output into the Cinematographer, and you're experimenting in two minutes.

How it works

The one required input is file_path, a multiline text field. The path is relative to ComfyUI's output directory - the default is AKKILLM/Project01/filename.txt, and if your project lives under output/AKKILLM/Project01/, that's the exact string you type. It joins the path, checks the file exists, reads it as UTF-8, and returns the contents.

One output: text_content (STRING). Wire it into anything that takes text - prompt fields, LLM agent inputs, file savers.

The error handling is the gotcha

Here's the thing that'll make you double-take: if the file doesn't exist, the node doesn't crash. It returns a string that starts with ERROR: File not found at the specified path: ... as your text_content. The workflow keeps running, and that error text flows downstream like it's legitimate content. So a typo in the path quietly poisons everything downstream. When your Cinematographer output reads like a filesystem error message, check this node's output string for the ERROR: prefix - that's the tell.

Install

Pack install:

cd ComfyUI/custom_nodes
git clone https://github.com/routhakash/AkkiNodes-LLM-Suite-for-ComfyUI

Or ComfyUI Manager → search "AkkiNodes LLM Suite" → install, run install.bat as admin on Windows, restart. No GGUF needed just for this node, though the pack as a whole wants one.

This and the Advanced loader are the two faces of the same job. Simple takes a path and just works; Advanced gives you a dropdown populated by a companion JS file, which is nicer when it works and a nuisance when it doesn't. If you ever hit the Advanced node's empty-dropdown issue, this is the reliable fallback - same output type, same relative-to-output paths, zero dependency on the pack's front-end bits.