Actions26
- Chat Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
This node, named "Telegram CoPilot," integrates with the Telegram API to perform various Telegram-related actions programmatically. Specifically, for the Group resource and the Get Supergroup Full Info operation, it retrieves detailed information about a specified Telegram supergroup. This can be useful for administrators or bots that need to fetch comprehensive metadata about a supergroup, such as its members, permissions, description, and other settings.
Common scenarios include:
- Automating group management tasks by fetching full details of a supergroup.
- Monitoring supergroup configurations or membership changes.
- Integrating Telegram supergroup data into workflows for reporting or notifications.
Example: A workflow could trigger this node to get full info on a supergroup when a new member joins, then use that data to customize welcome messages or update external databases.
Properties
| Name | Meaning |
|---|---|
| Supergroup ID | Identifier of the Supergroup to retrieve full information for. |
Output
The node outputs an array of JSON objects representing the response from the Telegram API for the requested supergroup full info. The structure typically includes detailed fields about the supergroup such as:
- Basic supergroup metadata (ID, title, username, etc.)
- Member counts and lists
- Permissions and roles
- Description and other configuration details
The output is purely JSON; there is no binary data output 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.
- Requires proper login/authentication via phone number and code before operations can be performed.
- The node depends on the TelePilot library and its connection/session management.
Troubleshooting
Session Closed or Unauthorized Errors:
If you see errors like "A closed client cannot be reused" or "Unauthorized," it means the Telegram session has expired or was terminated. The node will prompt to log in again using the login flow. Follow the guide at https://telepilot.co/login-howto to reauthenticate.Invalid Supergroup ID:
Providing an incorrect or non-existent supergroup ID may result in errors or empty responses. Verify the ID is correct.Missing or Invalid Credentials:
Ensure the API key credential is properly configured and valid.Login Required:
Before performing operations, ensure the node is logged in via the login operation using phone number authentication.
Links and References
- TelePilot Login Guide — Instructions for authenticating your Telegram account.
- Telegram API Documentation (general reference): https://core.telegram.org/bots/api