Overview
Telegram bots are created and owned through the official @BotFather. BotFather assigns the immutable bot identity and issues the HTTP API token used to authenticate the connection in Telestars.
- Create a new bot from the official Telegram service.
- Choose a recognizable name and valid username.
- Copy the complete API token securely.
- Know how to react if the token is exposed.
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 the verified @BotFather account in Telegram and send /newbot.
- Enter a clear display name that operators can recognize later in Telestars.
- Choose a unique Telegram username that ends in bot, then confirm creation.
- Copy the entire HTTP API token from BotFather without adding spaces or line breaks.
- Store the token temporarily in a secure place and paste it directly into Telestars.
- If anyone else sees the token, revoke or regenerate it in BotFather before connecting the bot again.
How it works
These are the product rules and states that matter for this workflow.
| What to know | Telestars behavior |
|---|---|
| Official account | Use only Telegram’s verified @BotFather account to create or manage a bot. |
| Username rule | BotFather requires a unique username with the Telegram bot suffix, while the display name can be more human-readable. |
| Token authority | Anyone holding the API token can authenticate as the bot, so it must be treated as a secret rather than a public username. |
| Telestars identity | Telestars verifies the token against Telegram and stores the returned bot identity for the workspace. |
Verify the result
- BotFather confirms that the bot was created.
- The username is the one you intend to connect and ends in bot.
- You have the complete API token and have not shared it with anyone.
Troubleshooting
| If you see this | What to check |
|---|---|
| The username is unavailable | Choose another unique username that still ends in bot; the display name does not need to change. |
| The token was copied incorrectly | Return to the bot in /mybots and copy or regenerate its token, then replace the value in Telestars. |
| The token was exposed | Revoke or regenerate it immediately in BotFather, then reconnect the new token in Telestars. |
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.