Send Message 🔽

Send Message is the simplest node in the ComfyUI Telegram Suite, and it's the one you'll actually use first. It fires a plain text message at a chat. "Done in 3:42." "LoRA baked in." A prompt echoed back so you can see what the workflow actually ran. That's the whole job, and it does it without any of the file-handling ceremony the image and video senders carry around.

How it works

Under the hood it's one call to Telegram's sendMessage method. The bot instance and chat_id come from the Telegram Bot node, the text goes into the request, and the API returns the message object it just created. Nothing cached, nothing queued - if the node runs, a message goes out, so it's usually sitting at the end of a workflow where it can only execute once generation is finished.

The inputs that matter

You're setting three things 95% of the time:

• bot and chat_id - wire both from your Telegram Bot node. This is why that node outputs a chat_id; you don't want to type numbers into every send node.
• text - a multiline string, 1 to 4096 characters. Wire it from anywhere: a plain STRING, the output of a prompt node, a filename from a Save node, even the message DICT of a previous send if you're feeling fancy.

The rest are the Telegram API's standard knobs, all with sane defaults. parse_mode lets you send HTML or Markdown so you can bold the important part (<b>done</b> with HTML mode). disable_notification defaults to true - silent, so a finished render doesn't blast your phone at 3am. protect_content blocks forwarding and saving of the message, which you mostly don't need for a status ping. message_thread_id is for forum topics; the default of -1 means "no topic" and the node quietly strips it before sending.

Outputs

message (a DICT with Telegram's full response - the message id, chat info, timestamps), message_id (INT), and trigger (the suite's execution-order signal; see the Send Chat Action article for how that works). The message_id is the one to keep: pair this node with Edit Message Text and you can update a single "still working…" message instead of spamming one per step.

Install and gotchas

Install is the pack install - Manager (search "ComfyUI Telegram Suite") or the one-liner:

cd ComfyUI/custom_nodes
git clone https://github.com/SwissCore92/comfyui-telegram-suite.git
cd comfyui-telegram-suite
pip install -r requirements.txt

The shared prerequisites apply: ffmpeg on PATH, a configured config.json, restart after editing it (full setup is in the Telegram Bot article). One thing that catches people: if parse_mode is left on "None", that's fine - the node drops it before calling the API. And if your message never arrives, check the console. The pack logs [Telegram Suite 🔽]: sendMessage(...) -> OK when it lands, and a sanitized error (no token, no chat id) when Telegram rejects it - usually a wrong chat_id or a bot that was never started. Send the bot any message in the chat first; Telegram ignores bots that haven't been "opened" by someone yet.