Set up Telegram integration using the discourse-chat-integration plugin

Yes I’m also experiencing this too. It will react to join/leave/pin events and I did make sure "Group Privacy is enabled.

Any updates on this? Much appreciated. @david

1 Like

Hello, We’re experiencing the same problem as well. The group privacy setting is enabled for our bot. However, it keeps sending:

New rule: /[watch|follow|mute] [category] [tag:name]
(you must specify a rule type and at least one category or tag)
- watch – notify this channel for new topics and new replies
- follow – notify this channel for new topics
- mute – block notifications to this channel

Remove rule: /remove [rule number]
([rule number] can be found by running /status)

List rules: /status

Help: /help

Every time someone join or leave, Is there any solution for this?

1 Like

Currently, the solution is to create a channel and set the bot to broadcast to that channel. Then link that channel with the group chat.

Although, I’d prefer a cleaner solution.


I’m having the same issue regarding the bot reacting to pin/join/leave events and posting the help message.

It also reacts to users (any user) tagging it or replying to its posts by re-posting the Chat ID.

There is also the fact that it tags Telegram users with a ‘@’, but using their Discourse username. These often don’t match. In my opinion it should mention the user name, but without using the @ symbol.

Given that I broadcast different filters to multiple telegram chats, the workaround of using a channel is not doable for me.

Is there someone working on this plugin that could take care of these issues? @david – sorry to annoy you, but maybe you can answer this question.

I am willing to spend some time and attempt to sift through the code, but I’m not very familiar with Ruby on Rails and that would take time to adjust.


getting an error 422 when testing it on groups or chanels.

the bot works perfectly on private chat with the bot itself. so the API is fine.

I noticed telegram gives you 10 digit chat ID for personal chats and 13 digits chat ID for groups or channels. this is the only difference i see.

anyone found a way to solve this ?

We’ve made the necessary changes and tested it for a number of days in multiple Telegram chats.

We took the liberty of creating a pull request:


Thank you for this plugin it sounds great.
I have installed it for telegram and it works, you can get messages when somebody publish in a category or publish in a group.

But I would like to receive system notifications (alerts) for example those that system sends when a backup fails, or when it advices you to upgrade to a new version.
It would be great to have them in telegram instead of email.
How can I achieve that?
Thank you.

I think you need this plugin instead:

1 Like

Thank you but reading the info it seemed that the other plugin is user oriented and thought to let users interact with discourse threads using telegram, receive answers to their posts, give likes and so.

I just want to receive discourse notifications to mods and admins in telegram, notifications when something goes wrong.
That is the most important for us. May be we implement the other funcionality in the future, but I prefer testing it with admin and mods messages.

In this plugin there is the option to send group notifications to telegram
I had thought that was what we needed.

But when I select group notification in channel rules, I just see some groups of users we have created.
In the list there is no system groups like admins, mods, staff, confidence level one, ando so.

@david I am trying to use your plugin to redirect messages thar are sent administrator and mods groups to corresponding telegram chat groups.
I have created the bot and included it in the chat groups and it works, the bot sends test messages.
The problem is that when i create the rule and try to select message group as the origin, in the list of grpups it only shows groups created by us, none of the system groups like admins, mods, staff or confidence level.
How can I solve this?
Thank in advance.