Actions27
- Chat Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
The node "Telegram CoPilot" provides a comprehensive interface to interact with Telegram via the TelePilot API. It supports various Telegram resources such as chats, messages, users, groups, contacts, and files. The node enables operations like retrieving chat details, sending messages (text, photo, video), editing messages, managing chat members, and more.
For the Chat resource with the Get Chat operation, the node fetches detailed information about a specific chat by its ID. This is useful for scenarios where you want to retrieve metadata or status of a particular chat in Telegram, such as fetching chat title, type, participants, or other attributes.
Practical examples:
- Fetching chat info before sending a message to verify chat existence.
- Retrieving chat details to display in dashboards or logs.
- Using chat metadata to trigger conditional workflows based on chat properties.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The unique identifier of the chat to retrieve information from. Example: "122323". |
Output
The output is a JSON array containing one object representing the chat information returned by the TelePilot API's getChat method. This object includes all available metadata about the chat, such as chat ID, title, type, participants, permissions, and other Telegram-specific chat details.
No binary data output is associated with this operation.
Example output structure (simplified):
{
"id": 123456789,
"title": "My Group Chat",
"type": {
"_": "chatTypeGroup"
},
"members_count": 42,
"permissions": { ... },
...
}
Dependencies
- Requires an active Telegram API authentication credential (an API key credential) configured in n8n.
- Depends on the TelePilot Node Connection Manager internally to manage Telegram client sessions.
- The node requires network access to Telegram servers via the TelePilot API.
Troubleshooting
- Session Not Logged In: If the Telegram account session is not logged in or expired, errors like "Please login" or "Session was closed or terminated" will occur. Resolve by performing the login process using the node's login operations or following the guide at https://telepilot.co/login-howto.
- Unauthorized Errors: These indicate invalid or expired credentials. Re-authenticate your Telegram API credentials.
- Invalid Chat ID: Providing a non-existent or malformed chat ID may result in errors or empty responses. Verify the chat ID correctness.
- Network Issues: Connectivity problems can cause timeouts or failures. Ensure stable internet connection.
- Command Usage: For login-related commands, use supported commands only (e.g., /start, /stop, /help).
Links and References
- TelePilot Official Login Guide
- Telegram API Documentation
- TelePilot GitHub Repository (for advanced usage and troubleshooting)