Nodes/ComfyUI-Notifications/Unified Notification
ComfyUI Node

Unified Notification

ComfyUI Notifications Node Guide

By royceschultz·Created 2 years ago·Updated about a year ago· 35
Unified Notification
  • any
    mode
    system_notificationtrue
    notification_textYour notification has triggered.
    play_soundtrue
    volume0.5
    filenotify.mp3

    Most people who install ComfyUI-Notifications end up wanting both a chime and a popup when a render finishes - and wiring two separate nodes for that is a bit silly. Unified Notification is the pack's answer: it folds the system notification and the play-sound chime into one node with toggles, so one wire off your Save Image node covers both. The README is blunt about why it exists - "convenience" - and that's really the whole pitch.

    How it works. Same shape as its siblings: an any input (a wildcard type that accepts anything) that you connect to whatever should finish right before this node fires, and no outputs - it's a terminal/output node, so ComfyUI runs it even though nothing downstream reads from it. Internally it's just doing what System Notification and Play Sound each do on their own, gated behind two booleans.

    The fields:

    • system_notification - boolean, on by default. Pops a browser notification (the OS-level banner) when the node fires.
    • notification_text - the message shown in that banner, defaults to "Your notification has triggered." - worth customizing if you're running more than one workflow so you know at a glance which one just finished.
    • play_sound - boolean, also on by default. Plays the chime alongside the popup.
    • volume - 0–1 slider for that chime, default 0.5.
    • file - the sound file, defaults to notify.mp3 (the one bundled with the pack); swap in your own by dropping it into custom_nodes/ComfyUI-Notifications/web/assets/ or pointing this at a direct audio URL.
    • mode - always fires on every run through the node; on empty queue holds off until your entire queue has finished, not just this one job - the one to use if you're batching a bunch of prompts and only want one notification at the very end.

    Turn either boolean off if you only want half the behavior - say, sound but no popup because you're in a shared office. If you want more control than that (separate mode settings for the sound vs. the popup, for instance), that's exactly what the standalone Play Sound and System Notification nodes are for; Unified trades that granularity for one node instead of two.

    Installing it. Through ComfyUI Manager - search "ComfyUI-Notifications" - or manually: cd ComfyUI/custom_nodes && git clone https://github.com/royceschultz/ComfyUI-Notifications, then restart ComfyUI. Nothing heavy to pull in: no models, no external services, just browser APIs and an audio file.

    Where this trips people up. Almost always the popup half, not the sound half. Browser notifications require the site to have been granted permission at least once - if you dismissed or blocked that prompt the first time ComfyUI asked, the browser generally won't ask again, and system_notification will silently do nothing even though the sound still plays fine. Check the notification permission icon in your address bar if the popup never shows. The other common mix-up is expecting mode: on empty queue to mean "this job is done" rather than "everything you've queued is done" - if you've got other prompts queued behind this one, both the sound and the popup wait for all of them to clear first.

    Categorynotifications

    Inputs (7)

    NameTypeDefaultDescription
    any*
    modeCOMBO2 options: always, on empty queue
    system_notificationBOOLEANtrue
    notification_textSTRINGYour notification has triggered.
    play_soundBOOLEANtrue
    volumeFLOAT0.50–1
    fileSTRINGnotify.mp3

    Outputs (0)

    No outputs