Telegram CoPilot icon

Telegram CoPilot

Your Personal Telegram CoPilot
Join our community

Actions33

Overview

This node integrates with the Telegram API via the TelePilot library, enabling automation and interaction with Telegram entities such as users, chats, messages, files, and groups. Specifically, for the Group resource and 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 workflows.
  • Fetching metadata or full details of a supergroup for reporting or monitoring.
  • Integrating Telegram group data into other systems or dashboards.

Practical example:

  • You want to get detailed info about a specific Telegram supergroup (e.g., member count, permissions, description) to display in your CRM or admin panel automatically.

Properties

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

Output

The output is 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 response to the getSupergroup or getSupergroupFullInfo method calls, typically including fields such as:

  • Basic supergroup info: id, title, username, type, status, etc.
  • Full info may include members count, administrators, permissions, description, sticker sets, and other metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an active Telegram API session authenticated via an API key credential (referred generically).
  • Uses the TelePilot library to manage connections and invoke Telegram API methods.
  • The node expects valid credentials with API ID, API hash, and phone number configured.
  • The Telegram client session must be logged in; otherwise, the node will throw login-related errors.

Troubleshooting

  • "Please login" error: Indicates that the Telegram client session is not authenticated. Resolve by running the login operation using the ChatTrigger node or following the login instructions at https://telepilot.co/login-howto.
  • "A closed client cannot be reused" error: The session was closed or terminated. Marked internally and requires re-login.
  • Unauthorized errors: Usually mean invalid or expired credentials; re-authenticate.
  • If the node returns empty or unexpected results, verify the correctness of the Supergroup ID.
  • Network issues or Telegram API rate limits can cause failures; retry or check connectivity.
  • Ensure the Telegram account has permission to access the requested supergroup info.

Links and References

Discussion