[ZBX-18235] Telegram send to group chat Created: 2020 Aug 11  Updated: 2020 Aug 12  Resolved: 2020 Aug 12

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: None
Affects Version/s: 5.0.2
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Arpad Zsoldos Assignee: Kristians Pavars
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Debian 10, Zabbix Server 5.0.2, using the build in Telegram media type.

Attachments: PNG File Screenshot 2020-08-11 at 17.36.03.png    

 Description   

Hi,

 

I am trying to integrate Zabbix with Telegram for notifications.

So far, so good, the notifications are being sent to the Telegram bot named: zabbix_natoora_bot

I received them and it is working fine here.

However, i woul dlike to send notifications in a group chat in Telegram, not to the bot.

I followed your instructions here: https://www.zabbix.com/integrations/telegram but still doesn't work. If i test and put the groupid to the test page it says "Bad Request: chat not found. But if i put my user id it works because it sends to the user.

 

I also tried to add to that group @zabbix_natoora_bot and then i run from the chat: /start@zabbix_natoora_bot and still says the same error, i have attached the screenshot.

 

Any ideas ? I tried to recreate everything twice.

 

 

 Comments   
Comment by Kristians Pavars [ 2020 Aug 12 ]

Hi Arpinator

 

Thanks for reaching out to Zabbix public bug tracker. I tried recreating the setup and it works fine for me to sending both to group and to bot user.

Have you copied the groupid correctly with the "-" sign if it has one?

And does your bot has permissions for that chat group and is added as administrator?

 

Regards,
Kristiāns

Comment by Arpad Zsoldos [ 2020 Aug 12 ]

Hi,

 

Yes, i havent put the "" because for the user is working without "" so i thought i don't need.

 

Sorry for the confusion, works well now.

 

Thanks for help, you can close the ticket now.

Generated at Tue May 20 07:43:37 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.