Actions26
- Chat Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
This node, named "Telegram CoPilot," provides extensive integration with the Telegram API, enabling automation and interaction with Telegram accounts. Specifically for the Group resource with the Get Supergroup 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 metadata or status about Telegram supergroups.
- Integrating Telegram group data into workflows for monitoring or reporting.
- Using supergroup info to trigger further actions in an automated pipeline.
For example, a user might input a supergroup ID to fetch its full details such as member count, permissions, or description, then use that data downstream in n8n for notifications or analytics.
Properties
| Name | Meaning |
|---|---|
| Supergroup ID | Identifier of the Supergroup to query. |
The property "Supergroup ID" is a string input where the user specifies the unique identifier of the Telegram supergroup whose information they want to retrieve.
Output
The node outputs a JSON array containing the response from the Telegram API for the requested supergroup information. The structure depends on the Telegram API's getSupergroup or getSupergroupFullInfo method responses, typically including fields like:
- Supergroup ID
- Title
- Description
- Member counts
- Permissions and settings
- Other metadata related to the supergroup
No binary data output is produced by 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 Telegram TDLib-based client managed internally.
Troubleshooting
- Session Not Logged In: If the Telegram session is not logged in, the node throws errors prompting the user to log in first using the login operation. Users should follow the guide at https://telepilot.co/login-howto.
- Closed Client Error: If the client session was closed or terminated, the node instructs to re-login.
- Unauthorized Errors: These indicate invalid or expired credentials; re-authentication is required.
- Invalid Supergroup ID: Providing an incorrect or non-existent supergroup ID will result in an error from the Telegram API.
- Network Issues: Connectivity problems may cause failures in invoking Telegram API methods.
Users should ensure their Telegram account is properly authenticated and the supergroup ID is valid.
Links and References
- Telepilot Login Guide — Instructions for logging in and managing Telegram sessions.
- Telegram TDLib Documentation — Underlying library used for Telegram API interactions.
- Telegram Bot API — General reference for Telegram API methods (note: this node uses TDLib, which is more comprehensive).