Load Document

Documents in ComfyUI sounds odd until you see the workflow it feeds. WAS Node Suite v3 has a whole document subsystem - Save DOC writes a container, Convert DOC to Plaintext and View DOC Metadata read it, and a document can be rendered, inspected or piped into text nodes. Load Document is the front door: it opens one document from disk and puts it on a DOC wire, markup, metadata and embedded files included. This is the pack making good on "whole folders through a graph."

Which formats, and what that means

The file menu lists every document in ComfyUI's input, output and temp folders, three folders deep, plus anything under paths.allow_read. Three kinds open:

• .wasdoc - the container Save DOC writes. It arrives exactly as the file holds it: markup, metadata, embedded files, byte-faithful.
• .docx and .odt - opened converted, not copied. The writing, tables, links and pictures come across; page geometry, headers, footnotes, comments and tracked changes do not. Those two read through python-docx and odfdo, which the error message names if either is missing.
• .pdf - never read. The description says so flat-out, which saves you hunting for a PDF path that doesn't exist.

Two gates matter. First, .docx/.odt reading sits behind the document_export feature group in config.yaml - if that group is off, the node can refuse them. Second, the conversion libraries aren't installed by default; the README has the one-liner:

python_embeded\python.exe -m pip install -r ComfyUI\custom_nodes\was-node-suite-comfyui\requirements\document_export.txt

That's the only optional dependency in the whole pack, and it only gates this document corner. It pulls python-docx, odfdo and xhtml2pdf (the last for Save DOC's .docx/.odt/.pdf export).

Outputs and the re-read trick

One output, the DOC wire - point it at View DOC Metadata to see what's inside, Convert DOC to Plaintext to turn it into a string for text nodes, or Save DOC to write it back out. One behaviour worth knowing: the document is read again whenever the file on disk changes. Edit the source document, re-run the prompt, and the graph picks up the new content without you hunting for a reload - genuinely useful for a "render this report" workflow where the text changes between runs.

Installing it

Load Document ships in WAS Node Suite:

cd ComfyUI/custom_nodes
git clone https://github.com/WASasquatch/was-node-suite-comfyui.git

or ComfyUI Manager → "WAS Node Suite v3", then restart. Requires ComfyUI 0.14.0+ and Python 3.10+.

Where people trip

Most friction is the format expectations. A .wasdoc is the round-trip format and behaves perfectly; .docx comes across as a conversion and quietly drops layout, so don't round-trip an office file through the graph and expect a byte-identical document back - that's what .wasdoc is for. If a .docx won't open, check the document_export feature flag before blaming the file, then check python-docx is installed. And if you're looking for PDF support, stop: it's never read, by design.