💬 TA Discord Link

This is the most honest node in the pack: it doesn't generate, transform, or save anything. TA Discord Link is a link button that lives on your canvas. Click it inside ComfyUI and it opens the pack author's Discord invite in your browser. That's it.

There's no info_schema to speak of - no inputs, no outputs, nothing to wire. It's a marker node, the same breed as a note or a bookmark, just with a job to do. The URL and the button label are configurable through a small browser-based editor the pack registers, so if the author's server changes address or you want the button to say something else, you can edit the config instead of waiting for an update. On disk that's a tiny JSON config file the node creates with defaults on first run.

Why would you want this? Mostly workflow hygiene. If you share your graphs - and this pack's whole design is built around sharing thomo.ART-style workflows - a Discord link on the canvas is a one-click path for anyone who loads your workflow to find you, report a bug, or ask what the heck a TA_MODEL_NAME wire is. It's the pack author's ko-fi-and-Discord link culture made into a node: a support channel embedded in the artifact instead of buried in a README.

Is it essential? No, and it knows it. But it's also zero-cost, it's clearly a v4-era addition to the pack, and if you're building a workflow you're going to distribute, dropping a contact node in a corner is a small touch that does real work. The pack also ships a TA Help Link node that opens its built-in wiki - same idea, different target. Between the two, a workflow can carry its own documentation and its own community channel.

Install. Same as the rest of the pack - no dependencies:

cd ComfyUI/custom_nodes
git clone https://github.com/tmode-1960/TA-ComfyUI-Nodes-Pack

or via ComfyUI Manager (search "TA ComfyUI Nodes Pack"), restart, and it shows up under thomo.ART/utils.

Gotchas. Don't expect any computation from it - if you wire anything into it, you'll find there's nothing to connect to, and that's correct. Also, because it renders a button that opens an external site, it's worth a second of thought in a workflow you share widely: the link goes to the pack author's server by default, not yours. And as always with this pack, the v1→v2 rename means old workflows built on TA v1 nodes need rebuilding regardless of what you do with this one.