⚙️ Telegram Config

What this node actually is

The ⚙️ Telegram Config node is a leftover from an earlier design of this pack. In the old days you dropped it into a workflow, typed your bot token, default chat ID, and LoRA routing into its widgets, ran the graph once, and it wrote a config/telegram_config.json file the pack read from then on. That design had a real problem: config nodes live inside workflows, and workflows get shared.

The current version fixes that by moving all configuration into ComfyUI's native Settings (gear icon → Telegram Sender). The TelegramConfig node still exists so old saved workflows load without error, but in the current source it's effectively a no-op - no inputs, no outputs, nothing to configure. The README is blunt about it: deprecated, use the Settings menu instead, and it "will be removed in a future version."

So the first thing to know is the one you actually need: you shouldn't reach for this node at all. If a workflow you loaded put it there, you can delete it.

The thing it used to do, done the modern way

If you came here because an old workflow references this node, here's the setup that actually works now:

1. Install the pack and restart ComfyUI (see the install steps below).
2. Open Settings (⚙ in the bottom-left) and find the Telegram Sender section.
3. Fill in Bot Token (from @BotFather), Default Chat ID, and optionally LoRA to Channel Mapping (one lora_name:chat_id per line), NSFW Channel ID, and Unsorted Channel ID.

Everything saves automatically to your ComfyUI user directory. If you have a legacy config/telegram_config.json file from the old version, the pack migrates it on first startup - and yes, once your values are in Settings you can drop the TelegramConfig node from the workflow for good.

Why the move matters: your token now lives in your local ComfyUI settings, marked as a secret, and never in the workflow file. Sharing a workflow JSON or a PNG with the workflow embedded no longer leaks your bot credentials. That's the whole point of the redesign - earlier Telegram sender nodes made people paste the token straight into the node and pray before sharing, and the community advice around those was basically "whatever you do, strip the token before you post anything."

Getting a token and chat ID

The BotFather part is unchanged: send /newbot, name your bot, and copy the token (123456789:ABC...). For a personal chat, message the bot once, then open https://api.telegram.org/bot<TOKEN>/getUpdates and read chat.id. For a channel, add the bot as an administrator, post once, and read the ID - channel IDs start with -100.

Installation

Via ComfyUI Manager: search ComfyUI-Telegram-Sender. Or manually:

cd ComfyUI/custom_nodes
git clone https://github.com/Sergey004/ComfyUI-Telegram-Sender
pip install requests pillow piexif

Restart ComfyUI. No model downloads.

Common issues

• "No bot token configured" - the token goes in Settings → Telegram Sender, not in a node. There is no config node anymore.
• Settings won't save - write-permission trouble on your ComfyUI user directory; watch the console for errors.
• Old workflows still show the node - harmless. It does nothing now; delete it once your values are migrated into Settings.
• "Invalid bot token" - check for stray spaces; the format is digits:letters.

The honest summary: this page is basically a tombstone. If you're setting up the pack today, skip this node entirely and configure it in Settings.