Connect your app to Telegram

Telegram lets your app reach people through a bot in private chats, groups, and channels. Connect a bot you own to Mythos, then ask Mythos to build notifications, an interactive workflow, or a support experience around it.

The connection is available while you build in the project chat and in your published app. It connects your app to Telegram; it does not create a way to chat with the Mythos builder from Telegram.

With Telegram, you can:

Send text, photos, documents, and other supported media.
Add buttons and keyboards and respond to button presses.
Set the bot’s commands and menu button, including a link to a Mini App.
Build an app that receives and responds to messages sent to the bot.
Deliver order updates, operational alerts, and reports to an intended chat.

Examples to build

These are starting points for apps and workflows Mythos can create. The bot connection supplies Telegram access; the app still needs the rules, data, and any schedule described in your prompt.

App idea	Prompt to try	What it adds
Order notifications	Send our team a Telegram message when a new order is placed, including the order number and total.	An order event in your app produces a message in the team chat.
Service alerts	Build a service-status dashboard and add a Telegram alert when a check detects an outage.	A monitoring workflow with a clear destination and alert condition. Ask for the checking schedule as part of the app.
Support inbox	Build a support dashboard that receives messages from our Telegram bot and lets staff reply.	A shared interface for conversations handled by your bot.
Daily summary	Create a daily sales summary and send it to our Telegram group each morning.	An app that collects the metrics, runs the schedule, and sends the report.
Threshold notifications	Let users choose an inventory threshold and notify our team in Telegram when stock falls below it.	A rule tied to your app’s data, with a message when the condition is met.

For any outgoing message, specify the destination and what should trigger it. For a customer conversation, explain how the app should identify the customer and which information the bot may reveal.

How a Telegram connection works

Each saved connection represents one bot and uses the bot token issued by Telegram’s official BotFather. It does not sign in to a personal Telegram account.

The bot can act only where Telegram permits it. A person needs to start a conversation with the bot before it can message them privately. Add the bot to the intended group or channel and give it the permissions needed there.

Multiple projects can be linked to a saved connection, but incoming messages need special care: Telegram supports one webhook per bot. A new webhook registration replaces the previous destination.

Connect Telegram to Mythos

You need a Telegram account, a bot token, and permission to create connections in your Mythos workspace. If the bot is already connected and shared with you, use its saved connection.

Telegram’s Bot API limits still apply. This connector does not enable paid broadcasts or paid suggested posts.

1. Create your bot

Open @BotFather in Telegram.
Send /newbot and follow its instructions.
Choose a name and a username ending in bot.
Copy the bot token BotFather gives you and store it securely.

The token gives access to your bot. Paste it only into the Bot token field in Mythos, not into the project chat or a public file. Telegram’s BotFather guide explains bot creation and management.

2. Save the connection

From the Dashboard, open Connectors and select Telegram. If no saved connection is available, the setup form opens.
Enter a Connection name, such as Order notifications.
Paste the token into Bot token. The Open BotFather link takes you back to Telegram’s bot management tool if needed.
Under Sharing, leave Private selected or choose Share with others. Grant access to selected members, or use Share with workspace.
Click Connect Telegram. Mythos checks the bot token before saving it.

In your project, open Chat actions (+) → Project connectors, select the saved Telegram connection, and click Use in this project. Ask Mythos to build the notification or bot workflow. Connections in Mythos explains project links and the agent’s approval settings.

Receive messages and commands

To respond to incoming messages, your app needs a public HTTPS address where Telegram can deliver them. Ask Mythos to build the receiving behavior and register that address as the bot’s webhook. Saving the bot token alone does not create a support inbox or an automatic reply.

For example:

Let customers message the bot with an order number. Check that the order belongs to that customer, then reply with its current status. Provide a help response for unknown commands.

If the bot stops receiving messages after being used in another project, check its webhook destination. The most recent registration wins. Telegram polling and an active webhook cannot be used for the same bot at the same time.

If sending fails, check that the recipient has started the bot, the bot belongs to the target group or channel, and its permissions allow posting. If only incoming messages fail, check the receiving address and the webhook’s latest error. See the Telegram Bot API for provider-specific errors and limits.

Limitations

Create and manage the bot through BotFather. Connecting a token does not create a bot for you.
This connection represents your bot, not a separate Telegram login for every app user.
Mythos does not automatically rotate the bot token. If you revoke it in BotFather, save the replacement in Mythos.
Message delivery, group privacy settings, and channel permissions remain subject to Telegram’s rules.

Manage your bot connection

Open Connectors → Telegram, then the saved connection. Use Linked projects → Unlink projects to remove selected project links. Disconnect stops Mythos from using the connection; it does not delete the bot or its chats in Telegram.

To change the token, choose Update bot token. Linked projects stay linked, but published bot features using the old credential stop working until they are set up again. Ask Mythos to set up those features with the updated connection and publish the change.