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 supergroups without manual intervention.
Practical example:
- A workflow that triggers on an event and fetches full info about a supergroup to log its current status, members count, or settings.
Properties
Name | Meaning |
---|---|
Supergroup ID | Identifier of the Supergroup to retrieve full information for. This should be provided as a string representing the unique ID of the supergroup. |
Output
The output is a JSON array containing the detailed information of the requested supergroup. The structure corresponds to the Telegram API's response for the getSupergroupFullInfo
method, which typically includes:
- Basic supergroup metadata (ID, title, description).
- Member counts and lists.
- Permissions and settings.
- Additional administrative and configuration details.
No binary data output is indicated for this operation.
Dependencies
- Requires an active Telegram API authentication token (API key credential) configured in n8n credentials.
- Depends on the TelePilot library and its connection manager to handle Telegram client sessions.
- The node requires a valid logged-in Telegram session; otherwise, it prompts for login via phone number and authentication code.
- Network access to Telegram servers is necessary.
Troubleshooting
Session Closed or Unauthorized Errors:
If the error message indicates "A closed client cannot be reused" or "Unauthorized," it means the Telegram session has expired or was terminated. The user must re-authenticate using the login process described at https://telepilot.co/login-howto.Invalid Supergroup ID:
Providing an incorrect or non-existent supergroup ID will likely result in an error from the Telegram API. Verify the ID before use.Missing Credentials:
Ensure that the required Telegram API credentials are properly set up in n8n; otherwise, the node will not execute.Login Required:
If the node returns messages prompting login, follow the instructions to authenticate via phone number and code using the ChatTrigger node integration.
Links and References
- TelePilot Login Guide — Instructions for authenticating Telegram accounts.
- Telegram API Documentation - getSupergroupFullInfo — Official Telegram API reference for the supergroup full info method.