Telegram CoPilotInstall

Overview

This node, named "Telegram CoPilot," provides a comprehensive interface to interact with Telegram via its API. It supports multiple resources such as chats, messages, users, contacts, groups, files, and login sessions. Specifically for the Chat resource with the Get Chat operation, it retrieves detailed information about a specific chat by its ID.

Common scenarios where this node is beneficial include:

• Automating Telegram chat management tasks.
• Fetching chat details for monitoring or logging purposes.
• Integrating Telegram chat data into workflows for customer support, notifications, or analytics.

Practical example:

• You want to retrieve metadata about a particular Telegram chat (e.g., group or private chat) to display in your dashboard or trigger further actions based on chat properties.

Properties

The property "Chat ID" is required and must be provided as a string representing the target chat's ID.

Output

The output is a JSON array containing the result of the invoked Telegram API method corresponding to the requested operation. For the Get Chat operation, the output JSON includes detailed information about the specified chat, such as its type, title, participants, permissions, and other metadata as returned by Telegram's API.

No binary data output is indicated for this operation.

Example output structure (simplified):

[
  {
    "_": "chat",
    "id": 123456789,
    "type": { "_": "chatTypePrivate" },
    "title": "Chat Title",
    "permissions": { ... },
    "last_message": { ... },
    ...
  }
]

Dependencies

• Requires an active Telegram API authentication credential (an API key credential with apiId, apiHash, and phoneNumber).
• Depends on the TelePilotNodeConnectionManager to manage Telegram client sessions.
• Requires proper login/authentication before performing operations; otherwise, it will prompt for login or throw errors.
• No additional external services beyond Telegram API are needed.

Troubleshooting

• Session Not Logged In: If the Telegram account session is not logged in or has expired, the node throws errors prompting to log in again. Use the login flow with the ChatTrigger node and follow the guide at https://telepilot.co/login-howto.
• Unauthorized Errors: These indicate invalid or expired credentials. Re-authenticate using the login commands.
• Closed Client Error: If the client session was closed unexpectedly, the node marks the client as closed and requires re-login.
• Invalid Chat ID: Providing an incorrect or non-existent chat ID may result in errors from the Telegram API.
• Command Not Supported: When using the login resource, unsupported commands return help instructions.

Links and References

• Telegram API documentation: https://core.telegram.org/api
• TelePilot login guide: https://telepilot.co/login-howto
• TelePilot official site: https://telepilot.co