Telegram CoPilotInstall

Overview

This node, named "Telegram CoPilot," provides extensive interaction capabilities with the Telegram API through a single unified interface. It supports multiple resources such as chats, messages, users, groups, contacts, files, and login sessions. The node enables operations like retrieving chat details, sending messages (text or photo), editing messages, managing chat members, and handling user authentication.

For the Chat resource with the Get Chat operation specifically, the node fetches detailed information about a particular chat by its ID. This is useful for scenarios where you need to retrieve metadata or status of a chat, such as in customer support bots, group management tools, or analytics dashboards that integrate Telegram data.

Practical examples:

• Fetching chat info before sending targeted notifications.
• Retrieving chat details to display in an admin panel.
• Verifying chat existence or properties before performing further actions.

Properties

Output

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

The node does not explicitly handle binary data for this operation.

Example output structure (simplified):

{
  "id": 123456789,
  "type": { "_": "chatTypePrivate" },
  "title": "Chat Title",
  "photo": { /* chat photo info */ },
  "permissions": { /* chat permissions */ },
  // ... other chat-related fields
}

Dependencies

• Requires an active Telegram API credential with appropriate API ID, API hash, and phone number configured.
• Depends on the TelePilotNodeConnectionManager to manage Telegram client sessions and authentication states.
• Requires the user to be logged in via the node’s login mechanism before performing chat operations.
• No external services beyond Telegram API are needed.

Troubleshooting

• Not logged in / Unauthorized errors: The node requires a valid Telegram session. If you see errors indicating unauthorized access or closed clients, re-login using the node’s login operation following the guide at https://telepilot.co/login-howto.
• Session closed or terminated: If the session was closed unexpectedly, the node will prompt to log in again. Use the login commands or connect a ChatTrigger node to handle authentication.
• Invalid Chat ID: Ensure the Chat ID provided exists and is accessible by the authenticated user.
• Network or API issues: Temporary Telegram API outages or network problems may cause failures; retry after some time.

Links and References

• TelePilot Login Guide
• Telegram API Documentation
• TelePilot GitHub Repository (for advanced usage and troubleshooting)