Feature request: Telegram bridge

[alexkorotysh]

Hi @l5yth,
Hope you’re doing well!

I was wondering if it might make sense to consider adding a Telegram bridge at some point. I think it could be a useful addition for notifications and integrations, but of course, just sharing it as an idea for consideration 🙂

A basic Telegram bridge usually works like this:

• Create a bot using Telegram via BotFather
• Get the bot token (API key)
• Decide where messages should be sent (chat ID, group, or channel) and from what protocol (meshtastic/meshcore) and mesh channel
• Implement a small service or webhook sender:
  • Send HTTP requests to Telegram Bot API (/sendMessage)
• Optionally:
  • Add formatting, alerts, routing logic
  • Handle incoming messages if two-way communication is needed

Simplified flow:

1. System event happens
2. Your service triggers a request to Telegram API
3. Bot delivers the message to a chat/channel

[l5yth]

Thanks for the suggestion. I don't have Telegram so I cannot implement this myself but if we implement it, we should add it to the matrix bot and make it configurable by protocol (e.g., matrix, telegram, signal, etc.)