AutoLink Converter

It doesn't compute anything. It tidies your graph.

Most nodes exist to transform data. This one exists to stop you from tearing your hair out over a graph that looks like a plate of spaghetti. AutoLink is the pack's frontend feature: it takes a direct wire connecting two distant nodes - say, a conditioning output on one side of the canvas feeding a sampler on the other - and converts that long, crossing link into a compact Set / Get pair. The wire becomes a short local connection plus a named token, and the graph becomes readable again.

The Converter node is the technical anchor of that feature. Its info_schema is nearly empty - no required inputs, no outputs, and a single optional arg input of type AUTOLINK_ARG. It's a placeholder the UI can point at while it rewires the graph. Under the hood the class literally does nothing (noop), because the work happens in the frontend JavaScript, not in the backend. It returns an empty tuple. That's the whole node.

What it means for you

If you've ever loaded a downloaded workflow and spent ten minutes trying to figure out which of the fifteen overlapping wires actually carries the prompt, you know the pain this exists to solve. The README's pitch is straightforward: "convert direct links into compact Set/Get nodes + restore when needed." Two directions:

• Link → Set/Get: long-range connections collapse into a short wire to a Set node, which emits a named value, plus a Get node anywhere else that resolves it.
• Restore: when you're done reading or editing, convert back to a direct link so the graph behaves exactly as before.

Because the conversion is reversible and the token is a plain value, the workflow keeps all its semantics - you're reorganizing the visual graph, not changing what it computes. The AUTOLINK_ARG type is the carrier for that token, and it's only meaningful inside this pack's AutoLink feature, so don't expect to wire it to anything else.

The honest take

This is a UI ergonomics tool with a deliberately fake node behind it, and that's fine - ComfyUI is full of these (think reroute boxes and group conveniences). It won't fix wrong values or broken graphs; it fixes legibility, which is its own kind of valuable when you're inheriting someone's 200-node video workflow. There's nothing to configure, nothing to tune, and you'll interact with it through a toolbar/context action in the pack's frontend more than by dragging the node onto the canvas.

Install is the pack install: ComfyUI Manager → search "IAMCCS", or:

cd ComfyUI/custom_nodes
git clone https://github.com/IAMCCS/IAMCCS-nodes.git

Then restart ComfyUI - and actually, restart matters more than usual here, because AutoLink's functionality lives in the web/ frontend directory and won't load until ComfyUI picks the new static files up. If you install and the AutoLink actions don't appear, a full restart (not just a workflow reload) is the first fix to try.