Telegram CoPilot icon

Telegram CoPilot

Your Personal Telegram CoPilot

Actions27

Overview

This node integrates with the Telegram API via a custom client manager to perform various Telegram-related operations. Specifically, for the Group resource and 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:

  • Fetching metadata or configuration details of a Telegram supergroup for monitoring or automation.
  • Integrating Telegram group data into workflows that require group info, such as analytics dashboards or notification systems.
  • Automating administrative tasks based on supergroup properties.

Example use case:

  • A workflow triggers when a new message arrives in a Telegram supergroup, then uses this node to fetch full info about that supergroup to decide further processing steps based on group settings or membership.

Properties

Name Meaning
Supergroup ID Identifier of the Supergroup to retrieve information for. This should be a string representing the unique ID of the Telegram supergroup.

Output

The node outputs an array of JSON objects 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 such as:

  • Basic supergroup metadata (title, description, member count, etc.)
  • Full info may include additional details like administrators, permissions, and other extended properties.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active Telegram API session authenticated via credentials containing API ID, API hash, and phone number.
  • Uses a custom connection manager internally to handle Telegram client sessions.
  • The user must have previously logged in through the node’s login mechanism or ChatTrigger node to establish a valid session.
  • Network access to Telegram servers is required.

Troubleshooting

  • Session Not Logged In: If the Telegram account session is not active or has expired, the node will throw errors prompting re-login. Users should follow the login instructions at https://telepilot.co/login-howto.
  • Unauthorized Errors: These indicate invalid or expired credentials; re-authentication is necessary.
  • Closed Client Error: Occurs if the internal Telegram client session was closed unexpectedly. The node suggests logging in again.
  • Invalid Supergroup ID: Providing an incorrect or non-existent supergroup ID will result in API errors or empty responses.
  • Network Issues: Connectivity problems can cause timeouts or failures in invoking Telegram API methods.

Links and References

Discussion