Salt Workflow Info

Two text boxes that don't touch your images at all - this is metadata, not processing. Salt Workflow Info lets you type a title and description for a workflow so that information lives in the graph itself, rather than in your head or a separate readme nobody opens.

How it works

It exists because of what this pack's team actually builds: Salt AI is a platform (getsalt.ai) for deploying ComfyUI workflows as Discord bots and, eventually, hosted APIs - they launched publicly in March 2024 with exactly that pitch. Once a workflow leaves your own machine and gets run by someone else, or served behind an endpoint, "what does this thing even do" stops being obvious just from looking at a tangle of nodes. SaltInfo is the answer: a title and description baked into the graph, readable by whoever's deploying or calling it, without needing to open the node canvas and reverse-engineer intent from wiring.

The inputs and outputs that matter

• workflow_title (required, STRING) - short, like a page title.
• workflow_description (required, STRING) - enough to tell an unfamiliar user what they're getting and roughly what inputs to expect, the way you'd write an API doc summary.

Outputs are title and description, the same text passed back out as separate STRING values - useful if something else in your graph (a metadata-save step, another display node) wants to reuse the same label instead of you retyping it.

How to install it

ComfyUI Manager: search SaltAI-Open-Resources or SaltAI, install, restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/get-salt-AI/SaltAI

then restart. Pure string node - no dependencies, no model.

Common issues & troubleshooting

"I added this node and nothing about my render changed." Correct, and expected. If you're running purely locally and never deploying through a platform that reads this metadata, this node has no functional effect on the actual output - it's documentation, not computation. Don't go debugging why it "didn't do anything"; it isn't supposed to.

Left both fields blank. They're required STRING inputs, and an empty string is technically valid, so the workflow will still run - it just defeats the entire point of the node. If you're bothering to add it, actually fill it in.

The README doesn't show a worked deployment example. This pack's own documentation is thin on how title/description actually surface once a workflow is deployed through Salt's platform specifically - that's a platform-side integration detail this repo doesn't spell out, so treat the node as "documented intent for later," not something with a visible local effect you can verify today.