# Send notifications to a Telegram bot

**URL:** <https://vaultwarden.discourse.group/t/send-notifications-to-a-telegram-bot/460>\
**Category:** Feature Requests\
**Created:** [December 9, 2020, 11:35pm UTC](https://vaultwarden.discourse.group/t/send-notifications-to-a-telegram-bot/460 "2020-12-09T23:35:45Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![aponsin](https://avatars.discourse-cdn.com/v4/letter/a/91b2a8/32.png) [@aponsin](https://vaultwarden.discourse.group/u/aponsin)\
**Post date:** [December 9, 2020, 11:35pm UTC](https://vaultwarden.discourse.group/t/send-notifications-to-a-telegram-bot/460/1 "2020-12-09T23:35:45Z")

</div>

Hello there,

Since sending e-mails requires some significant prerequisites, would it be possible to add a feature to send notifications to a Telegram bot instead (while keeping both features) of sending e-mail notifications?

I hope this idea will be adopted!

In advance, thank you!

---

<div class="post-metadata">

**Author:** ![BlackDex](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/blackdex/32/8_2.png) [@BlackDex](https://vaultwarden.discourse.group/u/BlackDex)\
**Post date:** [December 10, 2020, 10:37pm UTC](https://vaultwarden.discourse.group/t/send-notifications-to-a-telegram-bot/460/2 "2020-12-10T22:37:59Z")

</div>

That will be a bit difficult. Sending Telegram notifications also needs some information, like bot-name, verification etc… etc…

Also, it would deviate a lot from upstream bitwarden, which we try to match as close as possible regarding features.

---

<div class="post-metadata">

**Author:** ![aponsin](https://avatars.discourse-cdn.com/v4/letter/a/91b2a8/32.png) [@aponsin](https://vaultwarden.discourse.group/u/aponsin)\
**Post date:** [December 10, 2020, 11:23pm UTC](https://vaultwarden.discourse.group/t/send-notifications-to-a-telegram-bot/460/3 "2020-12-10T23:23:51Z")

</div>

Sending Telegram notifications needs two things:

- bot API key,
- chat id.

But OK, never mind.

---

<div class="post-metadata">

**Author:** ![BlackDex](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/blackdex/32/8_2.png) [@BlackDex](https://vaultwarden.discourse.group/u/BlackDex)\
**Post date:** [December 10, 2020, 11:59pm UTC](https://vaultwarden.discourse.group/t/send-notifications-to-a-telegram-bot/460/4 "2020-12-10T23:59:23Z")

</div>

Well, we live in an opensource world, nobody is stopping you from developing it your self, create a PR and see if it gets merged.

I think we have other developing items laying which could have attention instead of adding a different e-mail interface which transfers it to telegram instead.

---

<div class="post-metadata">

**Author:** ![jjlin](https://avatars.discourse-cdn.com/v4/letter/j/e19adc/32.png) [@jjlin](https://vaultwarden.discourse.group/u/jjlin)\
**Post date:** [December 11, 2020, 1:00am UTC](https://vaultwarden.discourse.group/t/send-notifications-to-a-telegram-bot/460/5 "2020-12-11T01:00:51Z")

</div>

Telegram notifications would be nice to have, but compared to email, I don’t think any chat platform is universal enough to merit specific support in bitwarden\_rs, especially considering there are not many people actively contributing code to the project.

A more generic solution like webhooks would probably make more sense for bitwarden\_rs. That would make it possible to pass events to some other program (e.g., a bot server) that can ingest the webhook payload and take an appropriate action (e.g., have the bot send a message).