Relay API Notice

The name sounds like it's going to nag you about a billing problem. It won't. RelayAPINotice is just a sticky note - a big editable text box on your canvas that ships pre-filled with the pack's own cheat sheet, and does absolutely nothing else. No API calls, no key, no outputs. It's the least interesting node in ComfyUI-relayapi and, honestly, one of the more useful ones.

Here's why. The rest of this pack is a mess of coupled dropdowns - task_type decides platform, which decides api_format, which decides which model names are even legal. Forget which endpoint string goes with which task and you're on the "Expecting value: line 1 column 1" train to nowhere. The Notice node sits there with the answer already typed in: which api_format values are valid for images, video, sound and text, plus the add/delete syntax for the custom fields in Relay API Settings (delete:modelname in custom_model, delete:url in custom_api_base).

That's the whole job. You drop it next to your Settings node, wire nothing, and it keeps the one fact you'll actually forget visible at all times.

What's in the box

The single input is message, a multiline STRING pre-filled with the author's notes (in Chinese, though you're free to overwrite it with your own). The pack's front-end JS draws it as a rounded, auto-wrapping box, so it reads like a note rather than a bare widget. That's it - no outputs, and the node isn't marked as an output node. You cannot wire it into a workflow; it's annotation only.

Which is fine. ComfyUI already lets you rename any node and pin a title, but that title is one line. When you want a paragraph of context sitting on the canvas - which endpoints match which task, what key format the relay wants, the delete commands - a dedicated text node is the cleaner answer. Think of it as the pack's equivalent of a comment block in code.

How to use it

Search "RelayAPI" in your node list and it's under the RelayAPI category alongside the generators. There's nothing to configure beyond the text. If you're setting up a workflow for someone else - or coming back to it after two months - paste the current relay's model list into it and you've saved yourself the reverse-engineering.

Installing the pack

The node ships with ComfyUI-relayapi, so install the pack once and you get all six nodes. Either use ComfyUI Manager (search "ComfyUI-relayapi") or:

cd ComfyUI/custom_nodes
git clone https://github.com/flywhale-666/ComfyUI-relayapi

Restart ComfyUI. There are no dependencies to pip-install and no model files to download - the pack uses only requests and Pillow, which ComfyUI already ships.

Gotchas

The only real trap is expecting it to do something. It won't: it has no outputs, it doesn't validate your Settings, and editing the text doesn't change anything about how the pack runs. If you drag one onto the canvas expecting a doc popup or a config panel, you'll be waiting a while. But if you want the pack's own endpoint cheat sheet pinned next to your Settings node while you figure out which api_format goes with which key, it's exactly what the name says: a notice.