Workflow LoRA Scanner

Let's be straight with you, because the node won't be. WorkflowLoRAScanner is a stub. It exists, it shows up in your node list under loaders/lora, it takes your inputs, and then it hands you back a canned string that amounts to "sorry, not implemented." If you Googled it because a workflow you downloaded references it, here's what you need to know: don't build anything on this node, and don't expect it to download a single LoRA.

What it claims to do

The node's own description says "Scans the current executing workflow for LoRA usage." The idea: a simple node that hooks into ComfyUI's execution system, looks at whatever workflow is about to run, and reports which LoRAs it references - a lightweight version of the pack's other automation. That's a reasonable thing to want. It's just not what this node is.

What it actually does

Its executed function returns one line: "Workflow scanning would require deeper integration with ComfyUI execution system." That's it. No scanning, no detection, no download. The author left the class in the pack's node mappings with a placeholder implementation - it even takes a trigger input (a string, default "scan") and a civitai_token that nothing ever uses. The only genuinely functional part is the passthrough input and output, which let you route any value through the node, so at least you can wire it into a graph without breaking the flow.

The inputs and outputs, for the record:

• trigger - a string that "triggers" the scan. It doesn't.
• civitai_token - accepted, ignored.
• passthrough (optional input, and output) - the one thing that works, a generic pass-through.

What to use instead

The good news: the pack has two nodes that actually scan workflows, and they share the exact same name- and JSON-parsing engine (the LoRAAutoDownloader class):

• LoRAAutoDownloader - paste the workflow's API-format JSON in, it finds and downloads everything missing. This is the reliable one.
• WorkflowLoRAInterceptor - hooks ComfyUI's execution queue so every workflow gets scanned automatically when auto-mode is on. Finer on paper, slightly fragile in practice, but real.

Either one does what the scanner's description promises. This node is development leftovers - the pack's node_config.json even lists it, but the README documents only four nodes and this isn't one of them. It's the fifth wheel.

Installing (and why you barely need it)

If you have the pack installed, you already have this node; it comes along for the ride:

cd ComfyUI/custom_nodes
git clone https://github.com/LargeModGames/comfyui-smart-lora-downloader

Restart ComfyUI. Its only dependency is requests, bundled with ComfyUI. If a downloaded workflow requires this specific node by name, installing the pack satisfies the dependency check and lets the workflow load - then swap the scanner out for a LoRAAutoDownloader the moment you actually want results. The scanner's real value is just as a stub that prevents "missing node" errors in someone else's workflow. Use it for that, and nothing else.