Actions27
- Chat Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
This node integrates with the Telegram API to perform various operations related to Telegram entities such as users, contacts, chats, messages, files, and groups. Specifically, for the Group resource and the Get Supergroup Full Info operation, it retrieves detailed information about a specified Telegram supergroup by its identifier.
Common scenarios where this node is beneficial include:
- Automating retrieval of comprehensive data about a Telegram supergroup for analytics or monitoring.
- Integrating Telegram group information into workflows that require group metadata.
- Building bots or services that need to access full details of a supergroup to make decisions or trigger actions.
Practical example:
- A workflow that fetches full info of a supergroup to display its description, member count, and settings in a dashboard.
- Automatically retrieving supergroup info before sending targeted messages or managing group memberships.
Properties
| Name | Meaning |
|---|---|
| Supergroup ID | Identifier of the Supergroup to retrieve full information for. This should be a string representing the unique ID of the supergroup. |
Output
The node outputs an array of JSON objects containing the response from the Telegram API for the requested operation. For the Get Supergroup Full Info operation, the output JSON includes detailed information about the supergroup such as its title, description, members, permissions, and other metadata provided by Telegram.
The exact structure depends on Telegram's API response but typically includes fields like:
id: The supergroup's unique identifier.title: The name of the supergroup.description: Text description of the supergroup.member_count: Number of members in the supergroup.- Other administrative and configuration details.
No binary data output is produced by this operation.
Dependencies
- Requires an active Telegram API authentication credential (an API key credential) configured in n8n.
- Uses an internal connection manager to handle Telegram client sessions.
- The node depends on the Telegram API being accessible and the user account being logged in via the node’s login mechanism.
Troubleshooting
- Session Not Logged In: If the Telegram session is not logged in, the node will throw errors prompting to log in again. Use the login commands or the ChatTrigger node to authenticate.
- Closed Client Error: If the client session was closed or terminated, the node suggests re-login. This can happen if the session expired or was manually disconnected.
- Unauthorized Error: Indicates invalid or expired credentials; re-authentication is required.
- Invalid Supergroup ID: Providing an incorrect or non-existent supergroup ID will result in an error or empty response.
- Ensure the Telegram API credentials are correctly set up and the node has permission to access the requested supergroup.