--- title: Messaging Integrations type: system status: active created: 2026-07-22 updated: 2026-10-02 verified_on: 2026-10-02 confidence: high tags: [messaging, telegram, discord, email, integrations] sources: [raw/configs/hermes-config-sanitized.txt, live-jobs-json] --- # Messaging Integrations ## Telegram - **Status:** enabled, active - **allowed_chats:** `-1004321904721` (primary), `1793951355` (DM), plus the remaining chat IDs required by both multiplexed profiles on the default adapter — verified 2026-09-30 - **Rich messages:** true - **Platform toolsets:** cli, telegram (full suite) - **Delivery targets seen in cron:** telegram, `telegram:1793951355`, `telegram:-1004321904721`, `telegram:-1004321904721:notifications`, `telegram:-1004321904721:102`, `telegram:-1004321904721:273`, `telegram:-1004321904721:346`, `telegram:-1004321904721:1030` - **Notes:** Primary delivery target for scheduled jobs ### Delivery target semantics (verified 2026-10-01) - A **bare `deliver: "telegram"` resolves to the home DM (`1793951355`)** — *not* to the primary group. It is not a "send to the main chat" shorthand. - To reach a forum topic you must use the full form **`telegram::`**, e.g. `telegram:-1004321904721:102`. - Consequence: a job that names a group topic ID but is actually pointed at the DM fails with `configured thread_id … was not found` / `Message thread not found`. **Two variants are observed, and they behave differently** (verified 2026-10-02 against `~/.hermes/cron/executions.db`): - `Message thread not found` — hard failure, **the message is lost** (the 2026-09-30 incident variant). - `configured thread_id for telegram: was not found; delivered without thread_id` — a **thread-less fallback send** does occur, yet the run is still recorded as `last_status: delivery_failed` / `delivery_outcome: failed`. Content reaches the DM; the delivery is marked failed anyway, so the job record reads like a lost message. - Do not assume "delivery failed" means the message never arrived — check the error variant before reporting a report as missing. ## Discord - **Status:** enabled, streaming true - **Platform:** `hermes-discord` - **Platform toolsets:** cli, discord ## Email - **Status:** connected - **Libraries:** himalaya CLI available - **Platform toolsets:** cli ## Slack - **Status:** available (toolsets: cli, slack-platform) - **Config noted:** slack entries in config but Slack enabled status unclear from config grep ## Other Platforms Available - **Mattermost:** toolsets present (`hermes-mattermost`) - **Google Chat:** toolsets present (`hermes-google_chat`) - **QQ:** toolsets present (`hermes-qqbot`) - **Signal:** toolsets present (`hermes-signal`) - **WhatsApp:** toolsets present (`hermes-whatsapp`) - **ntfy:** noted in memory config outputs but runtime status unverified - **Yuanbao:** toolsets present (`hermes-yuanbao`) - **Home Assistant:** homeassistant-platform enabled ## Known Issues - **Telegram thread-delivery failures — resolved 2026-09-30.** Jobs `fad5a86979d4` and `1b23c042e17d` reported `configured thread_id 34795 … was not found`, and `c8d52904e1d6` reported `Message thread not found` (`last_status: delivery_failed`). Root cause was the *target*, not the topic: those jobs used a bare `deliver: "telegram"`, which resolves to the home DM where group topic IDs do not exist. `1b23c042e17d` and `c8d52904e1d6` were retargeted to `telegram:-1004321904721:102` and verified end-to-end. See [[systems/scheduled-tasks]]. - **Three jobs still deliver to the home DM via a bare `telegram` target** (`0e753e9720fd`, `fad5a86979d4`, `066bb5191280`). **No longer theoretical — two of them failed delivery on 2026-10-01:** `066bb5191280` (02:11) and `0e753e9720fd` (09:01) both recorded `delivery_outcome: failed` with the thread-less-fallback variant above, in the same failure class as the 2026-09-30 incident. Retarget them to `telegram:-1004321904721:`. See [[systems/scheduled-tasks]]. ## Multi-bot group chat (open question, raised 2026-09-30) Anthony asked whether his other Hermes instances (the estate VMs/CTs) could share a group chat. - **Preferred shape:** a Telegram supergroup with **one forum topic per bot**, so each agent posts into its own thread and no two bots share a message stream. Mattermost was floated and rejected. - **Estate reachability:** CT460's Hermes serves the WebUI/API on `:9119` (locally fronted by nginx on `:19119`). Whether the other estate hosts expose `:9119` still needs checking before any fan-out design. - **Status:** design question only — nothing has been deployed or changed. ## Related - [[systems/hermes-agent]] - [[systems/scheduled-tasks]] - [[infrastructure/tailscale]]