EZ Notify
A desktop ping when the queue finally finishes
- trigger
EZ Notify is the pack's "the render is done" bell. It fires a desktop notification when its trigger input changes - so you can tab away from a long queue and get a ping the moment your image is ready, instead of checking back every thirty seconds like a bird watching a nest.
Two inputs, no outputs:
- trigger (any type) - the execution gate. Wire the output of your generation into this. New output → notification. No trigger, no notification; it's an explicit design, not a bug.
- message (STRING, default
Job done) - the text shown in the notification.
It's marked as an output node, so ComfyUI treats it as a legitimate end of the graph. That matters: you can hang it off a SaveImage or EZ Generate Save the same way you'd add a second save, and the graph still queues normally.
How it works
On execution it sends a system notification with title "EZ Notify" and your message, at low urgency, via the desktop-notifier Python library. It doesn't poll, it doesn't watch the queue - it's a pure "when I run, I ping" node, and the trigger input is what makes it fire at the right moment. That's also why the timing feels right: the trigger changes when the upstream node produces its output, which is when the render is actually done.
When it's worth it
Honestly? It earns its keep in exactly one situation: long jobs. Video generations, big upscale batches, or an overnight queue of a hundred images. If your renders are twenty-second txt2img runs you're watching anyway, the notification is just another popup. But for anything where you'll walk away, it's the difference between waiting at the screen and doing something else. The default Job done message is fine - though if you run several queues with different nodes, setting a message per node (Batch done, Upscale done) makes the ping actually informative.
The Linux caveat
The one real rough edge: desktop notifications need a notification daemon. On Windows and macOS the standard plumbing is there, but on minimal Linux setups (especially headless servers or bare window managers without a notification service), the node can run fine and produce nothing - the library's send silently goes nowhere. If you're on Linux and no notification appears, check that your desktop environment has a notification daemon running (most do). It's a system thing, not a node bug.
Installing it
It ships with the Prompt Helpers pack - and it's why the pack's requirements include desktop-notifier, one of only two Python dependencies. In ComfyUI Manager search "Prompt Helpers" (Pauan/comfyui-prompt-helpers), install, restart. Manual:
cd ComfyUI/custom_nodes
git clone https://github.com/Pauan/comfyui-prompt-helpers
Then restart ComfyUI (ComfyUI Manager handles the desktop-notifier install; if installing manually, pip install desktop-notifier covers it). No model downloads; requires ComfyUI 0.8.0+.
Inputs (2)
| Name | Type | Default | Description |
|---|---|---|---|
| trigger | * | When this input changes, it will show the notification. | |
| message | STRING | Job done | The message which will be displayed in the notification. |
Outputs (0)
No outputs