Get Bot Info
telegram.get_me
ActionChat & messagingconnection required
Calls the Telegram API with the connection's credentials.
Read the bot's own identity and capabilities from its token.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Telegram
- Secret shape
- the bot token, or {"token": "…"}
- Resolved by
- config.connection_id, else node.connection_id
Configuration
This node takes no configuration beyond its connection.
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok True when Telegram accepted the call. | boolean | true |
id Numeric id of the bot. | number | — |
username The bot's @username, without the @. | string | — |
first_name The bot's display name. | string | — |
can_join_groups Whether the bot may be added to groups. | boolean | — |
bot The full User object getMe returned. | object | — |
{
"bot": {},
"can_join_groups": false,
"first_name": "",
"id": 0,
"ok": true,
"username": ""
}Notes
- chat_id is a numeric chat/user id or an @channelusername. A bot can only message a user who started it, or a group/channel it has been added to.
- The bot token sits in the request URL, so it is redacted out of every error message and dry-run report these nodes produce.
- Telegram answers HTTP 200 even for failures; the node reads the {'ok': …} envelope and raises on ok:false with Telegram's own description.
- This is the same call the connection self-test makes, so it is the cheapest way to check a token from inside a workflow.
See Get Bot Info run in a workflow.
In a technical demo we add the Telegram connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.