---
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)
- **Rich messages:** true
- **Platform toolsets:** cli, telegram (full suite)
- **Delivery targets seen in cron:** telegram, `telegram:1793951355`, `telegram:-1004321904721:1030`, `telegram:-1004321907D2:346`, `telegram:-1004321904721:273`
- **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_id `34795` for `telegram:1793951355` not found — one cron job delivered without thread_id

## Related
- [[messaging-integrations]]
- [[scheduled-tasks]]