Audio Notify Latent Trigger

Audio Notify Latent Trigger is the trigger node in ComfyUI-Audio-Notifier that takes a LATENT, plays a sound, and returns nothing. It's the dead-end version of Audio Notify Latent: same "sampling is over" signal, minus the passthrough - the latent goes in, a sound comes out, and the data path stays exactly where it was.

This is the node for the situation where you want to hear that the KSampler finished but you don't want to restructure anything. The natural layout is a branch off the sampler:

KSampler
├── VAE Decode
└── Audio Notify Latent Trigger

The trigger watches the latent, and the moment the sampler produces it, you get the chime. Because it's a trigger, the VAE Decode wire is untouched - you didn't have to insert anything into the path that matters. That's the honest trade versus the passthrough: Audio Notify Latent guarantees ordering by sitting in the wire; this one keeps the graph clean at the cost of only telling you "ready," never "decoded."

Keep the pack's core caveat in mind: a trigger fires when its input data is ready, not when the workflow is done, and a branch running parallel to VAE Decode carries no ordering guarantee. The latent being ready is essentially the sampling-done moment, which is what most people want - but if you need to know the decode finished too, hang the trigger downstream of the decode's result instead.

Inputs

• latent - the LATENT that triggers the sound.
• notification_enabled - mute the node.
• delay_seconds - hold the chime.
• repeat - 1–100 plays.
• blocking_playback - off by default (background thread); on to wait for playback.
• enable_sound_path / sound_path and enable_sound_name / sound_name - sound source: absolute path, or a file in the pack's sounds/ folder.
• fallback_to_system_beep - beep if nothing resolves, on by default.

No outputs.

Install and gotchas

No dependencies, no models. Clone and restart the backend:

cd ComfyUI/custom_nodes
git clone https://github.com/uni-miao/ComfyUI-Audio-Notifier.git

Restart the ComfyUI backend process, not just the browser tab. Pack-wide gotchas: the sounds/ folder ships empty, so add files (or use an absolute sound_path) and restart before the dropdown has choices; and audio always plays on the machine running the backend - if that's a remote box, that's where the chime comes out, not your laptop. .wav files are the most reliably supported format.