On Complete Play Sound:
OnCompletePlaySound plays a notification sound when the node executes, helping you notice that a workflow has reached this point without watching the screen. It uses Pygame to play the bundled assets/finished.mp3 file on the machine running the workflow. The sound is started during execution; the node does not wait for playback to finish, and it does not confirm that you heard it.
On Complete Play Sound Input Parameters:
any
This required connection lets you place the notification after another step in your workflow. It accepts any connected data type, so you can connect the result of the step you want to precede the sound. The node does not inspect or change the value; when it executes, it starts the same bundled sound regardless of what the connection carries. There is no minimum, maximum, default value, or list of options.
On Complete Play Sound Output Parameters:
This node has no output sockets. It starts sound playback as an action and does not pass the connected value onward or return an audio file or playback status.
On Complete Play Sound Usage Tips:
- Connect
anyto a step near the end of the work you want to monitor. The sound starts when this node executes, which is not necessarily when every other branch of a workflow has finished. - Make sure the machine running the workflow has working audio output and an audible volume. The sound plays there, not necessarily on the device displaying the workflow.
- Keep
assets/finished.mp3in the location expected by the installed node. This node has no setting for choosing another sound or adjusting its volume.
On Complete Play Sound Common Errors and Solutions:
ModuleNotFoundError: No module named 'pygame'
- Explanation: The Python environment running the workflow cannot import Pygame, which this node needs for playback.
- Solution: Install Pygame in that same Python environment, then restart the workflow application.
pygame.error: mixer not initialized or an audio-device initialization error
- Explanation: Pygame could not prepare its audio mixer. This may happen when the machine has no usable audio device or its audio setup is unavailable.
- Solution: Check that the machine running the workflow has a working audio device, confirm its audio settings, and restart the application. On a headless server, audio playback may require additional audio configuration.
FileNotFoundError or a Pygame error mentioning finished.mp3
- Explanation: The node could not load the bundled sound file from its
assetsfolder. - Solution: Check that
assets/finished.mp3exists alongside the installed node files in the expected location. Restore or reinstall the node package if the asset is missing.
A Pygame error while loading finished.mp3
- Explanation: The sound file was found but could not be decoded or played. The file may be damaged, or the installed audio setup may not support it.
- Solution: Restore the original bundled file and check that audio playback works in the environment running the workflow.
No sound, with no visible error
- Explanation: Playback may have started on a different machine, the volume may be muted, or the connected workflow step may not have caused this node to execute.
- Solution: Check the volume and audio output on the machine running the workflow, then confirm that this node actually executes when you run the workflow.
