Actions26
- Chat Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
This node, named "Telegram CoPilot," provides a comprehensive interface to interact with Telegram via its API. It supports multiple resources and operations, including user management, contacts, chats, messages, files, and groups. Specifically, for the Group resource, it allows retrieving information about supergroups.
The Get Supergroup Info operation fetches detailed data about a specified supergroup by its identifier. This is useful in scenarios where you need metadata or configuration details of a Telegram supergroup, such as its title, description, member count, or permissions.
Practical examples:
- Automating the retrieval of supergroup details to monitor group settings.
- Integrating Telegram supergroup info into dashboards or reports.
- Using supergroup metadata to trigger workflows based on group attributes.
Properties
| Name | Meaning |
|---|---|
| Supergroup ID | Identifier of the Supergroup to retrieve information about. |
Output
The output is a JSON array containing the response from the Telegram API for the requested operation. For the Get Supergroup Info operation, the JSON object includes detailed information about the supergroup identified by the provided Supergroup ID. This typically contains fields such as the group's ID, title, status, member counts, permissions, and other metadata defined by Telegram's API.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for Telegram (referred generically as "an API key credential").
- Uses an internal connection manager to handle Telegram client sessions.
- The node depends on the Telegram API and requires the user to be logged in via phone number authentication before performing operations.
- Proper session management is necessary; users must log in using the login operations before accessing group info.
Troubleshooting
- Session Not Logged In: If the Telegram account is not logged in, the node will throw errors prompting the user to log in first. Use the login commands or nodes to authenticate.
- Closed Client Error: If the client session was closed or terminated, the node suggests re-login to restore the session.
- Unauthorized Errors: These indicate invalid or expired credentials; re-authentication is required.
- Invalid Supergroup ID: Providing an incorrect or non-existent supergroup ID may result in errors or empty responses.
- Ensure that the API key credential has sufficient permissions to access group information.
Links and References
- Telegram API Documentation
- Telepilot Login Guide (for authentication instructions)
- Telegram Bot API (general reference for Telegram interactions)