Audio Notify Text

Audio Notify Text is the string passthrough node in ComfyUI-Audio-Notifier: it takes a STRING, plays a sound, and forwards the same string unchanged. It's the sibling of Audio Notify Text Trigger - same "ding when text is ready" idea, except this one keeps the data flowing, which makes it the better fit when the string still has somewhere to go.

Strings sit at the tail of most workflows - the output of a prompt or dynamic-text node, a caption, a generated filename. If that string is destined for a Show Text, a save-with-metadata chain, or anything else, this node slots into the wire: play a sound when the string is ready, then hand it along. The text physically passes through the node, so whatever receives it can't run until the string actually exists. That's the same ordering guarantee as the other passthroughs, and it's what makes the node useful for timing.

Worth noting how the input behaves: text is a STRING with forceInput set, so it must be wired from an upstream node - you can't type a literal. That's consistent with the pack's philosophy: the chime fires when real data is ready, not when you feel like it.

Inputs and output

• text - the string to pass through.
• 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 the sound before forwarding.
• enable_sound_path / sound_path and enable_sound_name / sound_name - pick a sound via absolute path or from the pack's sounds/ folder.
• fallback_to_system_beep - beep if nothing resolves, on by default.

One output: the unchanged STRING.

Choosing between Text and Text Trigger

If the string is a dead end for you - you only care that it exists, and nothing downstream needs it - the Audio Notify Text Trigger is the lighter choice (input only, no output). But if the string is feeding a display or save node anyway, use this one: you get the same sound and you don't have to reroute the wire to a separate branch. The trigger can't forward anything, so it would force you to run the string to a second destination separately.

Install and gotchas

No dependencies, no models. Clone and restart:

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 still apply: the sounds/ folder ships empty, so drop files in and restart before the sound_name dropdown has anything to pick (or use an absolute sound_path); and audio always plays on the machine running the backend - not necessarily your browser machine. No sound at all usually means the backend box's volume, or a missing ffplay for non-WAV files.