Overview
Connecting a token registers the Telegram bot inside the active Telestars organization. Telestars uses Telegram’s bot identity, while the optional workspace display name helps your team recognize it.
- Register the bot in the intended workspace.
- Confirm the resolved Telegram username before continuing.
- Use a clear internal display name.
- Keep the token out of normal team communication.
Before you start
- Access to the official @BotFather bot and the Telegram account that owns the bot.
- A Telegram Business profile where the bot should handle private conversations.
- Permission to add and manage bots in the Telestars workspace.
Step by step
- Open My Bots in the workspace that should own the bot and start the connect-bot action.
- Paste the complete API token issued by BotFather into the token field.
- Optionally add a clear workspace display name that distinguishes the creator or purpose.
- Submit the connection and wait for Telegram identity verification to finish.
- Compare the username shown in My Bots with the username in BotFather before configuring Secretary Mode.
- If the token must be replaced, regenerate it in BotFather and update the connection before further testing.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| Workspace scope | The bot is registered to the active organization, so verify the selected workspace before submitting the token. |
| Identity source | The Telegram username comes from the bot token; an internal display name does not change the Telegram identity. |
| Connection is not launch | A successfully registered token still needs Secretary Mode, Telegram Business permissions, and product readiness before AI replies can run. |
| Token security | The token is an authentication credential and should only be entered in the dedicated connection flow. |
Verify the result
- The new bot card appears in My Bots.
- The card’s @username exactly matches BotFather.
- No token value is visible in normal dashboard content after registration.
Troubleshooting
| If you see this | What to check |
|---|---|
| Invalid token | Copy the complete token again from the official BotFather and ensure there are no spaces or missing characters. |
| The wrong bot appears | Stop configuration, verify the BotFather token belongs to the intended username, and reconnect the correct credential. |
| The connect action is unavailable | Confirm that your workspace membership and role allow bot management, or ask an owner/admin to connect it. |
Best practice
Use one clearly named BotFather bot per intended profile, keep tokens private, and verify every connection with a real message from a second account.