简易通知 (Simple Notify)

You queue a big batch, alt-tab to something else, and come back forty minutes later to find it finished thirty minutes ago. SimpleNotify is this pack's fix for that: drop it anywhere in your graph, wire literally anything into it, and it fires a notification - and, optionally, a sound - the moment execution reaches that point.

It ships inside ComfyUI-Danbooru-Gallery, a 23-node collection that's mostly about pulling images and tags off Danbooru and cleaning up prompts. SimpleNotify is one of the small "workflow control" utilities the pack throws in alongside things like group-mute managers and value switches - nothing Danbooru-specific about it. It's the generic "let me know when this is done" node, and it happens to live here because that's where its author put it.

How it works

SimpleNotify is an output node - ComfyUI's term for a node that always runs, whether or not anything downstream needs its result, and that counts as a valid finishing point for the queue. It takes any input, fires its notification/sound as a side effect, and passes that same input straight through unchanged. That pass-through is the trick: you can drop it in the middle of an existing chain - say, between a VAE decode and a Save Image - without breaking the wire, instead of having to dead-end a whole separate branch just to get a ping.

One thing worth internalizing about how ComfyUI actually runs a graph: an output node fires when its own inputs are ready, not when your whole queue finishes. If your graph branches - a second, independent chain still has ten minutes of sampling left - a SimpleNotify wired only into the first branch will ping you while the second branch is still grinding away. Put it after the slowest branch, or after the last thing you actually care about finishing, not just wherever's convenient to wire.

Inputs and outputs

• any (in, wildcard) → any (out, wildcard) - plug in anything: an image, a latent, a string. It comes out the other side untouched.
• message - the notification text, defaults to "任务已完成" ("Task completed"). Change it if you're running several graphs at once and want to tell them apart at a glance.
• volume - 0 to 1 in steps of 0.1, default 0.5. Only matters if sound is on.
• enable_notification / enable_sound - two independent booleans, both on by default. Turn either off for just the popup with no noise, just a sound with no popup, or (both off) effectively mute the node without deleting it.

Installing it

Via ComfyUI Manager, search "ComfyUI-Danbooru-Gallery" and install. Manually:

cd ComfyUI/custom_nodes
git clone https://github.com/Aaalice233/ComfyUI-Danbooru-Gallery.git
cd ComfyUI-Danbooru-Gallery
pip install -r requirements.txt

then restart. This node itself doesn't need much, but the requirements file (requests, aiohttp, aiosqlite, psutil on top of Pillow/torch/numpy) is one shared install for all 23 nodes in the pack - run it in full rather than trying to cherry-pick.

Common issues & troubleshooting

Labels are in Chinese. This pack's front end defaults to Chinese - the README lists multi-language support as one of its built-in JS extensions. Other users have found a gear/settings icon that switches it to English; if message's default text or a widget label looks unfamiliar, that's why, not a broken install.

It fires too early, or seems to fire "for nothing." See the branch-order note above - this is almost always about where in the graph you wired it, not the node misbehaving. Move it downstream of whatever you actually want to be notified about finishing.

Node doesn't appear after install. Standard pack-wide checklist: confirm the folder path is exactly ComfyUI/custom_nodes/ComfyUI-Danbooru-Gallery, the pip install finished clean, you restarted, and there's no import error in the console on boot.

Notification doesn't visibly do anything. The README doesn't document the delivery mechanism (an OS-level toast vs. an in-browser popup), so I can't tell you exactly what to expect on your setup. If nothing happens, first check that enable_notification and enable_sound are actually on for that specific node instance - the boolean widgets won't warn you if both are quietly off.