Telegram CoPilotInstall

Overview

This node acts as a Telegram client interface, enabling users to interact with the Telegram API through various predefined resources and operations. It supports a wide range of Telegram functionalities such as user management, chat handling, message sending/editing/deleting, file operations, group management, and custom raw requests.

The Custom Request operation allows users to send arbitrary JSON-formatted requests directly to the Telegram API, providing maximum flexibility for advanced use cases not covered by other specific operations.

Common scenarios where this node is beneficial:

• Automating Telegram messaging workflows (sending messages, media, or actions).
• Managing Telegram chats, groups, and contacts programmatically.
• Retrieving detailed information about users, chats, or messages.
• Executing custom Telegram API calls that are not natively supported by other operations.
• Integrating Telegram interactions into broader automation pipelines.

Practical example:

• A user wants to send a custom Telegram API request to fetch detailed statistics or perform an action not exposed by standard operations. They can input the exact JSON request in the "Request (JSON)" property and execute it via the Custom Request operation.

Properties

Output

• The output is a JSON array containing the results of the executed Telegram API calls.
• For the Custom Request operation, the output will contain the parsed JSON response from the Telegram API corresponding to the submitted request.
• The structure of the output JSON depends entirely on the Telegram API method invoked.
• If the node handles binary data (e.g., sending audio files), the binary data is managed internally but not explicitly outputted in this operation.
• Errors or status messages related to the request execution are also returned in the JSON output when applicable.

Dependencies

• Requires a valid Telegram API authentication credential (an API key/token with necessary permissions).
• Depends on an internal connection manager to handle Telegram client sessions.
• Uses the Telegram TDLib-based API client under the hood.
• No additional external services beyond Telegram are required.
• The node expects proper configuration of credentials and session management to maintain active Telegram connections.

Troubleshooting

Common issues:

• Not logged in / Unauthorized errors: Occur if the Telegram session is not authenticated or has expired. Users must log in using the login operations before making API calls.
• Session closed errors: If the client session was closed or terminated unexpectedly, the node will prompt re-login.
• Invalid JSON in Request (JSON): Malformed JSON input will cause parsing errors; ensure the JSON is valid and correctly formatted.
• Telegram API errors: Errors like "User restricted receiving of video messages" or "File reference expired" may occur depending on Telegram's restrictions or state.

Error messages and resolutions:

• "Please login: https://telepilot.co/login-howto": Indicates the Telegram account is not logged in. Follow the linked guide to authenticate.
• "Session was closed or terminated. Please login again": The current session is invalid; re-authenticate.
• "Invalid file ID" or "File reference has expired": The referenced file is no longer valid; refresh or resend the file.
• "Cannot send messages to this chat": Permission issue; verify chat permissions.
• JSON parse errors: Check the syntax of the "Request (JSON)" input.

Links and References

• Telegram TDLib Documentation
• Telepilot Login Guide
• Telegram Bot API Reference (for general API understanding)

Note: This summary is based solely on static analysis of the provided source code and does not include runtime behavior or dynamic imports.