Telegram CoPilotInstall

Overview

This node integrates with the Telegram API via a custom client to perform various Telegram-related operations. Specifically, for the Group resource and the Get Supergroup Full Info operation, it retrieves detailed information about a specified Telegram supergroup. This can be useful for automation workflows that need to gather metadata or configuration details about large Telegram groups (supergroups), such as member counts, permissions, or other group settings.

Practical examples include:

• Automatically fetching full info of a supergroup to monitor its status or settings.
• Using the retrieved data to trigger alerts or updates in other systems when group properties change.
• Integrating Telegram group data into dashboards or reports.

Properties

The property "Supergroup ID" is a string input where you provide the unique identifier of the Telegram supergroup whose full information you want to retrieve.

Output

The node outputs an array of JSON objects representing the response from the Telegram API for the requested supergroup full info. The structure typically includes comprehensive details about the supergroup, such as:

• Basic group metadata (title, description)
• Member counts and lists
• Permissions and roles
• Other configuration details specific to the supergroup

The output is provided in the json field of the node's output data. There is no binary data output for this operation.

Dependencies

• Requires an active Telegram API authentication credential (an API key and related login credentials).
• Depends on a custom Telegram client connection manager internally managing sessions and API calls.
• The user must be logged in via the node’s login mechanism before performing this operation.
• No additional external services are required beyond Telegram itself.

Troubleshooting

• Session Not Logged In: If the Telegram session is not authenticated, the node will throw errors prompting to log in first. Use the node’s login operation to authenticate.
• Closed Client Error: If the client session was closed or terminated, the node suggests re-login.
• Unauthorized Errors: These indicate invalid or expired credentials; re-authentication is necessary.
• Invalid Supergroup ID: Providing an incorrect or non-existent supergroup ID may result in errors or empty responses.
• Network Issues: Connectivity problems with Telegram servers can cause timeouts or failures.

To resolve these issues:

• Ensure proper login using the node’s login commands.
• Verify the correctness of the supergroup ID.
• Check network connectivity.
• Follow the provided guide at https://telepilot.co/login-howto for detailed login and usage instructions.

Links and References

• Telegram API Documentation
• TelePilot Login Guide