Nodes/ComfyRage/🔔Alert
ComfyUI Node

🔔Alert

Go make tea — Alert rings when your ComfyUI render is actually done

By rakkarage·Created 9 months ago·Updated 26 days ago· 0
🔔Alert
  • any

    A long video render ties up your GPU for twenty minutes, and ComfyUI will sit there silently until it's done - no chime, no popup, nothing. You either babysit the screen or you wander off and discover the run finished ages ago. Alert is the two-second fix: a tiny output node you wire to the end of the graph that fires a browser notification and plays a sound the moment it runs.

    That's the whole job. And the nice part is that "when it runs" is exactly the right trigger: since ComfyUI executes a node only after everything feeding it finishes, a single Alert placed after your final output node rings precisely when the entire workflow is complete. Not when it started, not at some guessed interval - done.

    How it works

    The Python side of Alert is almost aggressively simple: it accepts any input, does nothing with it, and returns no outputs. All the actual work happens in the pack's frontend extension, which hooks the node's execution event and does two things - plays a bundled alert sound (alert.mp3 ships inside the pack) and fires a browser Notification. If you've never granted notification permission for the ComfyUI tab, it requests it on the first run.

    The input accepts anything because it's a wildcard socket - the value it receives is irrelevant, only the fact of arrival matters. That's why you can wire a string, an image, a model, anything into it. Whatever you hook up, the bell rings when the upstream work is done.

    Inputs and outputs

    One input, no outputs:

    • any (any type) - a wildcard that matches anything. Wire in whatever happens to be at the end of your graph; the value is ignored.

    That's it. There's nothing to configure on the node itself.

    Installing it

    Part of ComfyRage - zero pip dependencies, no models, public domain. ComfyUI Manager → search ComfyRage → Install, then restart. Manual:

    cd ComfyUI/custom_nodes
    git clone https://github.com/rakkarage/ComfyRage
    

    Restart and look under the rage category.

    The two things that bite

    Both are browser behavior, not the node's fault. First, autoplay policy: browsers block audio until you've interacted with the page, so the very first Alert in a fresh tab may log "Audio playback blocked" and stay silent until you've clicked around. Click once anywhere and subsequent alerts chime normally. Second, the notification banner needs your permission - the node asks on first run, and if you clicked "blocked" in a moment of distraction, you'll need to re-allow notifications for the ComfyUI tab in your browser settings.

    Honest take: if you're always at your desk, this is a nice-to-have. If you run long jobs and leave, it's one of those small QoL nodes that quietly pays for itself - and at this pack's install cost (a single clone, no dependencies), it's free to try alongside the more interesting prompt nodes.

    Categoryrage

    Inputs (1)

    NameTypeDefaultDescription
    any*

    Outputs (0)

    No outputs