Get Chat Member
telegram.get_chat_member
ActionChat & messagingconnection required
Calls the Telegram API with the connection's credentials.
Read one member's status and rights in a chat.
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
2 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
chat_id The chat to look in: a numeric chat/user id, or an @channelusername. | string | Yes | — | — | — |
user_id Numeric Telegram id of the user to look up. | integer | Yes | — | ≥ 1 | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok True when Telegram accepted the call. | boolean | true |
status creator, administrator, member, restricted, left or kicked. | string | member |
user_id Numeric id of the user. | number | — |
username The user's @username, when they have one. | string | — |
member The full ChatMember object, as returned. | object | — |
{
"member": {},
"ok": true,
"status": "member",
"user_id": 0,
"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.
- Looking up anyone other than the bot itself is only guaranteed to work while the bot is an administrator of the chat.
See Get Chat Member 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.