Start Discord Bot

Most ComfyUI nodes run once and finish. This one is different: Start Discord Bot opens a live connection to Discord and keeps it running, turning your agent workflow from a one-shot pipeline into something that sits and listens for messages continuously. It's how comfyui_LLM_party lets you deploy an agent as a Discord bot, rather than just chatting with it inside ComfyUI's own interface.

How it works

Running this node authenticates a Discord bot using a token from Discord's Developer Portal and starts it listening in whatever server you've invited it to. Unlike most nodes in a ComfyUI graph, which execute and hand off their output immediately, this one keeps a persistent connection alive for as long as the workflow is running - it's the "start the bot" step, not a single request-and-response. Once it's up, other nodes in the pack (discord_send, discord_file_monitor) interact with the same live connection to send messages and watch for incoming ones.

The inputs and outputs that matter

• token - your Discord bot's authentication token, from the Developer Portal's Bot section. This is a real credential, not a display name or invite link - treat it accordingly.
• function_name - a JSON array naming which capabilities the bot exposes (the default example is ["ping", "add"], a toy pair meant to show the format). This is where you list which of your workflow's functions the bot should make callable.
• is_enable - toggle the bot on or off.
• One output: is_success - a boolean telling you whether the bot actually connected. Check this before assuming everything downstream is working; a bad token or a Discord-side permission problem fails here, not loudly elsewhere.

How to install it

• ComfyUI Manager - search "comfyui_LLM_party", install, restart.
• Manual - cd ComfyUI/custom_nodes && git clone https://github.com/heshengtao/comfyui_LLM_party, then restart.

Then pip install -r requirements.txt from inside the comfyui_LLM_party folder, in your ComfyUI Python environment (python_embeded\python.exe -m pip install -r requirements.txt on portable Windows). The real setup work is on Discord's side, not ComfyUI's: create an application in the Discord Developer Portal, add a bot to it, copy the bot token, enable whatever intents your bot needs (message content, in particular, since Discord gates that behind an explicit opt-in), and invite the bot to your server with the right permissions.

Common issues & troubleshooting

is_success comes back false. Start with the token - a copy-paste error or a regenerated token (Discord tokens can be reset from the Developer Portal, which invalidates the old one) is the most common cause. After that, check the bot's intents: Discord requires you to explicitly enable privileged intents like message content in the Developer Portal, separate from just having a valid token.

Bot connects but never responds to anything. Check the bot actually has permission to read and send messages in the specific channel you're testing in - server-level bot permissions and channel-level overrides are two different things in Discord, and a bot can be "in" a server without being able to see a particular channel.

Treat the bot token as seriously as an API key. Anyone with your token can fully control the bot - read messages it can see, send as it, potentially access whatever data your workflow exposes through it. Custom-node ecosystems have a well-documented history of credentials leaking through shared workflow files; don't export or share a workflow JSON with a live token sitting in the token field.

The pack won't load at all. Separate from this node, comfyui_LLM_party has a real, current install issue where nodes fail to import after a Manager install - usually a CUDA/PyTorch mismatch with no clear compatibility list. Check that first if discord_bot isn't in your node browser.