Send Notification (Mobile)

If you've ever queued up a 20-minute video render and wandered off, you know the itch: you want a ping the moment it's done. Send Notification (Mobile) is that ping - a node that fires a native Windows desktop notification when the workflow reaches it. Slap it at the end of a long render and you can stop babysitting the progress bar.

The honest preface: this ships in ComfyUI-Mobile, a small early-stage pack from a solo dev (Soze Inc, the same person behind the ComfyUI_Soze nodes you'll see recommended in help threads). The pack README is literally one line: "actively under development and is not functional as a stand alone install." That disclaimer applies to all three nodes in the pack, and this one is the roughest of the three.

How it works

The name is a little misleading - it doesn't call any API and needs no key. The node just shells out to a Windows executable bundled in the repo (notifier/sozenotifier.exe), passes your message as a command-line argument, and hands back whatever the exe printed. That's the whole mechanism.

Inputs and outputs

The one you actually set is message - the notification text. There are two optional wrappers, messagePrefix and messageSuffix, if you want a standard prefix or suffix around whatever flows into the middle. The send_media checkbox is declared in the schema but isn't wired into the node's function in the current code - don't expect it to do anything yet.

The node returns two STRING outputs: output (the notifier's stdout) and error (its stderr). Wire the error output into a core Show Text node if you want to see why a launch failed.

Install

Same as any custom node. ComfyUI Manager, search "ComfyUI-Mobile", or:

cd ComfyUI/custom_nodes
git clone https://github.com/SozeInc/ComfyUI-Mobile

Then restart ComfyUI. requirements.txt is just requests - no model downloads, no heavy dependencies.

Where it bites

Three things, all grounded in the current code:

1. Windows only. The notifier path is hardcoded with backslashes and a .exe. On Linux or macOS this node will not work.
2. The exe name doesn't match. The code launches notifier\mobilenotifier.exe, but the repo actually ships sozenotifier.exe. On a fresh clone the launch fails until you rename the binary.
3. You're running a bundled binary. This is the ecosystem's uncomfortable truth (see the LLMVISION incident): a custom node runs code with your user privileges, and here that includes an unsigned .exe from the repo. Only run it if you're OK trusting the author.

Verdict

If you're on Windows and want a native toast when a job finishes, the idea is right - but as shipped it's early-stage and needs a rename before it works. Most people end up happier with ntfy or a Discord webhook, which work from any OS and don't need you to fix a binary name first.