This module allows to respond telegram chats as a telegram bot.
This way, a group of users can respond customers or any other set of partners in an integrated way.
It is not intended to be integrated on default chatter as users don't need to review again when one has responded.
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Connect Odoo to Telegram so a team can chat with Telegram users from Odoo and reply as a bot. Messages, photos, files, stickers and locations are exchanged automatically between Telegram chats and Odoo conversations.
This module adds Telegram as a new gateway type in the existing mail gateway settings. On the gateway form, when the type is Telegram, a dedicated "Telegram configuration" tab appears with step-by-step instructions to create a bot with BotFather, paste its token, and set a webhook key and secret. An extra "Telegram security key" field can be enabled so that new conversations are only created when a user sends the command /start followed by that key.
Once connected, incoming Telegram messages are turned into Odoo conversation messages: text, photos, documents, contacts, stickers (converted to animated images) and locations (shown as a Google Maps link) are all supported. Each Telegram user is matched to a partner or guest, and replies sent from Odoo are delivered back to the Telegram chat as a bot; edited messages are updated on Telegram too. If sending fails, the message is marked with an error and the reason is recorded.
In the messaging interface, Telegram messages show a paper-plane icon and a Telegram avatar, and delivery status is visible. The module touches the gateway settings (mail.gateway), conversations (discuss.channel) and message notifications.
Depends on
Required by other modules
Models and fields (2)
- mail.gateway · extends an existing modelgateway_type, telegram_security_key
- mail.gateway.telegram · new model
Text generated by AI (DeepSeek) from reading the Odoo 19.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 3 confirmed, 6 with no information of 9 versions.
Sources · Odoo 16.0
Confirmed on 2026-11-03 in branch 16.0 of OCA/social.
terminal Installation and usage
OCA documentation · Odoo 19.0Configuration
Source · Odoo 19.0Create the bot
- Create a Bot on telegram
- Create a broker following the examples on with the TOKEN provided
Configure Odoo
- Access on debug mode
- Access Settings \> Technical Settings \> Email \> Mail Gateway.
- Access Telegram and start a converstation with BotFather.
- Create a bot using the command /newbot. The system will ask for a bot name. Remember that it needs to end with the word bot.
- Copy the token to access the HTTP API to the token field.
- Define Webhook key an webhook secret of your choice in its corresponding field, in order to secure the connection.
- Press save button and the integrate webhook smart button will appear.
- Press the Integrate webhook button.
- If you want to add an extra layer of security, you can check Has New Channel Security and define a Telegram security key. New chats will be created only with the command /start SECURITY_KEY.
Limitations
The Webhook functionality can only be used if your system is accessible from website. On local installations it might be problematic as Telegram will not be able to contact your system. In that case, you might need to create a telegram bot that will send data to you on an external process with the following code.
from telegram.ext import Filters, MessageHandler, Updater
import requests
dp = Updater(YOUR_TOKEN)
def message_callback(update, _context):
requests.post(YOUR_CONTROLLER, json=update.to_dict())
dp.dispatcher.add_handler(MessageHandler(Filters.all, message_callback))
dp.start_polling()
dp.idle()Usage
Source · Odoo 19.0- Access Gateway
- Wait until someone starts a conversation with your bot.
- Now you will be able to respond and receive messages to this person.
No verified information in OCA: Installation.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.