Get AutoLink

If you've built a large ComfyUI workflow, you know the pain: ten nodes, forty edges, and the graph looks like a plate of spaghetti you're afraid to touch. The AutoLink system is IAMCCS's answer - instead of dragging a connection across the whole canvas, you put down a Set node next to the source and a Get node next to the destination, and the two talk without a visible wire. GetAutoLink is the retrieval side of that pair.

Here's the thing you need to know up front: it's a virtual node. The source literally says these nodes are "purely frontend - they do nothing in Python." All the logic lives in JavaScript in the pack's web/ directory. The Python class exists only so ComfyUI knows the node type and can place it on the canvas. That's not a bug - it's the entire design, and it's why the node has zero inputs and zero outputs in its schema.

How it works

You place an IAMCCS_SetAutoLink next to whatever produces a value, place this GetAutoLink where you want that value consumed, and the frontend JS routes the data between them invisibly. ComfyUI's execution engine handles the actual data flow; the AutoLink JS handles keeping the two visually linked and letting you convert back to real edges when you want.

The README describes the feature as "convert direct links into compact Set/Get nodes + restore when needed." So the practical flow is: build normally, then use the AutoLink converter to collapse long straight-line connections into Set/Get pairs. Your graph goes from ten crossed wires to two tidy pairs, and when you need to debug, you convert back.

There are companion pieces - IAMCCS_SetAutoLink (the producer), an IAMCCS_AutoLinkConverter (the UI tool that does the converting), and IAMCCS_AutoLinkArguments (a config stub) - and the source notes it's a 1:1 reimplementation of the KJ nodes' Set/Get/Converter functionality. If you've used those, this is the same muscle memory in the IAMCCS/AutoLink category.

Inputs that matter

None. It's a virtual placeholder - anything you see on the node is set up by the frontend when you create the pair. If you're looking for a port to plug into, you're looking at the wrong node.

Install

Ships with IAMCCS-nodes:

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

Or ComfyUI Manager → "IAMCCS" → install → restart. The JS lives in web/ and loads automatically; no extra deps.

Gotchas

Because the logic is frontend-only, these nodes are fragile across ComfyUI frontend changes - the ecosystem history here is littered with node packs that broke when upstream rewrote the UI layer, and this is exactly the kind of pack that's exposed. If a workflow with AutoLinks suddenly stops linking after a ComfyUI update, that's likely why. And since virtual nodes carry no data themselves, they don't survive being exported to a graph that strips JS behavior. They're a workflow-hygiene tool for your own big graphs, not a portability feature.