All nodes/Integrations/Telegram

Telegram Chat Info

Information about a chat and its members. Actions: chat (metadata), member_count (the exact number of members), administrators (the exact list of admins), member (one user's status), known_members (an APPROXIMATE roster assembled from recorded observations — the Bot API cannot enumerate members, so lurkers are missing), bot_rights (what the bot itself may do: delete messages, ban). Requires a Telegram Config, except for known_members, which is answered from our own tables.

Telegram Chat Info▶

Telegram ConfigSuccess

Error

Type in the graph: telegram_chat_info

Exec

An error branch can be enabled (expose_error_output) to handle failures on their own path.

Try it

Minimal working workflow

Entry

Telegram Chat Info▶

Exit▶

Execute
Execute + Data

Press “Copy nodes”, open the editor and hit Ctrl+V on the canvas.

Runs as pasted

When to use it

This node answers “what chat is this”, “who are the admins here”, “what is this member’s status” and “what may the bot itself do here”. The last one is the most common use: check the rights before a branch reaches Moderate or Manage Chat, instead of turning a Telegram refusal into a failed run.

How it works

One node with an Action field, because the Bot API’s membership surface is small and fragmented. The exact answers are getChat, the member count, the list of administrators and one user’s status. Enumerating every member is something the Bot API cannot do at all, so the observation roster is assembled from the platform’s own recording and is incomplete by construction.

The bot-rights action additionally returns can_read_all_group_messages — that is the privacy-mode signal. When it is false, group-history recording stays empty no matter how often you switch it on.

Common mistakes

Reading the roster as a full list. A member who never posted and joined before the bot arrived is simply missing. For an exact figure use the member-count action.
Only the chosen action’s field is filled; the rest stay empty: chat, member_count, administrators, member, known_members, bot_rights.
A Telegram refusal stops the node. That is deliberate: the most common refusal is “the bot is not a member of this chat”, which is exactly the fact being asked about. For softer handling, turn on the error output and draw the branch.
Chat ID is numeric only — @channelusername is not accepted. A blank field means the chat of the running Telegram turn, so a run started from web chat or a schedule stops with an error.
Another user’s status is reliable only when the bot is an administrator. An ordinary member gets noticeably less back from Telegram.
The roster is the one action that never calls Telegram. It works without a bot at all, but it does need group-history recording to have been enabled.

Inputs

Port	Wire	Payload	Notes
Telegram Config`telegram_config`	Data`data`	—	shown when connection_source ≠ "auto"

Outputs

Port	Wire	Payload	Notes
Success`output`	Execute + Data`execute_data`	`object`
Error`on_error`	Execute + Data`execute_data`	—	shown when expose_error_output = true

Configuration

Field	Type	Default	Description
Connection source`connection_source`	`string`	`auto`	Where this node gets its connection. 'From the run context' uses what the platform already knows (the Telegram bot this workflow is deployed to / this workspace's own file store) and needs no wiring. 'External connection' shows the resource port so a config node can be wired into it. Options: `auto` — From the run context, `external` — External connection (wire a config node)
Action`action`	`string`	`chat`	chat — chat metadata (getChat); member_count — the exact number of members; administrators — the list of admins; member — one user's status; known_members — a roster assembled from recorded observations (approximate: the Bot API cannot enumerate members, so lurkers are missing); bot_rights — the bot's own rights in the chat. Options: `chat` — Chat metadata (getChat), `member_count` — Exact member count, `administrators` — List of administrators, `member` — Status of one member, `known_members` — Roster from observation (approximate), `bot_rights` — What the bot itself may do here
Chat ID`chat_id`	`string`	`""`	Numeric Telegram chat_id (an @username is not accepted here). Blank = the chat of the running Telegram turn. Templates are supported. supports templates
Limit`limit`	`integer`	`200`	Maximum number of roster rows to return. shown when action = known_members
User ID`user_id`	`string`	`""`	Numeric Telegram user_id. Templates are supported. supports templates shown when action = member

Shared fields

Every node has these three — the platform adds them, not the node author.

expose_error_output — When enabled, show an execution output to connect nodes that run if this step fails.