Telegram CoPilot icon

Telegram CoPilot

Your Personal Telegram CoPilot

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 and the Get Supergroup Full Info operation, it retrieves detailed information about a Telegram supergroup identified by its unique ID.

Common scenarios where this node is beneficial include:

  • Fetching comprehensive metadata about a Telegram supergroup for monitoring or analytics.
  • Automating administrative tasks that require knowledge of group details.
  • Integrating Telegram group data into workflows for customer support, community management, or content distribution.

Example use case:

  • An automation workflow that triggers when a new message arrives in a supergroup, then uses this node to fetch full info about that supergroup to log or analyze its properties.

Properties

Name Meaning
Supergroup ID Identifier of the Supergroup to retrieve full 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 Full Info operation, the output JSON contains detailed information about the specified supergroup, including but not limited to:

  • Basic supergroup metadata (e.g., title, description).
  • Member counts and status.
  • Permissions and settings.
  • Possibly additional nested objects describing administrators, banned members, and other relevant group details.

No binary data output is associated with this operation.

Dependencies

  • Requires an active Telegram API authentication credential (an API key/token) configured in n8n.
  • Depends on the TelePilot library and its connection manager to handle Telegram client sessions.
  • The node expects the user to be logged in via the TelePilot login mechanism before making API calls.
  • No external environment variables beyond the Telegram API credentials are required.

Troubleshooting

  • Error: "Please login" or "Unauthorized"
    This indicates the Telegram session is not authenticated or has expired. Resolve by performing the login process using the appropriate login operation or node, following 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 necessary.

  • Invalid Supergroup ID
    If the provided supergroup ID is incorrect or does not exist, the Telegram API may return an error or empty result. Verify the ID before running the node.

  • Network or API errors
    Temporary network issues or Telegram API rate limits can cause failures. Retrying after some time or handling errors gracefully in the workflow is recommended.

Links and References

Discussion