Files
agent-estate-wiki/systems/messaging-integrations.md
T

60 lines
2.9 KiB
Markdown

---
title: Messaging Integrations
type: system
status: active
created: 2026-07-22
updated: 2026-07-22
verified_on: 2026-07-22
confidence: high
tags: [messaging, telegram, discord, email, integrations]
sources: [raw/configs/hermes-config-sanitized.txt]
---
# 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
## 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 on `telegram:1793951355` (2026-09-30):** jobs `fad5a86979d4` and `1b23c042e17d` report `configured thread_id 34795 … was not found`, and `c8d52904e1d6` reports `Message thread not found` (`last_status: delivery_failed`). Content generation succeeds — only the thread target is wrong. Fix: recreate the topic, or clear `thread_id` on those jobs. 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]]