Actions30
- Chat Actions
- Custom Request Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
This node integrates with the Telegram API via the TelePilot library, enabling automation and interaction with Telegram entities such as users, chats, messages, groups, and files. Specifically, for the Group resource with the Get Supergroup Info operation, it retrieves detailed information about a Telegram supergroup by its identifier.
Common scenarios where this node is beneficial include:
- Automating Telegram group management tasks.
- Fetching metadata or full details of a supergroup for reporting or monitoring.
- Integrating Telegram group data into workflows, e.g., syncing group info to databases or CRM systems.
Practical example:
- You want to get detailed information about a specific Telegram supergroup (e.g., member count, permissions, description) to display in your dashboard or trigger other actions based on group status.
Properties
| Name | Meaning |
|---|---|
| Supergroup ID | Identifier of the Supergroup to retrieve information for. This should be the unique numeric ID of the supergroup. |
Output
The node outputs an array of JSON objects representing the response from the Telegram API for the requested operation. For the Get Supergroup Info operation, the output JSON contains detailed information about the supergroup, including but not limited to:
- Basic supergroup properties (ID, title, username).
- Status and permissions.
- Member counts.
- Description and other metadata.
The exact structure depends on the Telegram API response but generally includes all available fields describing the supergroup.
No binary data output is produced for this operation.
Dependencies
- Requires an active Telegram API session authenticated via an API key credential (referred generically as "an API key credential").
- Uses the TelePilot library internally to manage connections and invoke Telegram API methods.
- The node expects the user to have completed login/authentication steps using the provided credentials before executing operations.
- No additional external services are required beyond Telegram's API.
Troubleshooting
Error: "Please login" or "Unauthorized"
This indicates that the Telegram session is not authenticated or has expired. The user must perform the login process using the ChatTrigger node combined with the login operation as described in the guide at https://telepilot.co/login-howto.Error: "A closed client cannot be reused"
The internal Telegram client session was closed unexpectedly. Re-login is required.Invalid Supergroup ID
If the provided supergroup ID is incorrect or does not exist, the Telegram API will return an error. Verify the ID is correct.Network or API errors
Temporary network issues or Telegram API rate limits may cause failures. Retrying after some time or handling errors gracefully is recommended.
Links and References
- TelePilot Login Guide — Instructions for authenticating Telegram sessions.
- Telegram API Documentation - Supergroups — Official Telegram API reference for supergroup objects (note: TelePilot uses TDLib, so structure may differ slightly).
- n8n Documentation — General guidance on using n8n nodes and workflows.