Actions27
- Chat Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
This node, named "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 handling chat sessions.
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 when you want to retrieve metadata or status of a specific chat in Telegram.
Common scenarios:
- Fetching chat details to display or log chat information.
- Integrating Telegram chat data into workflows for customer support or notifications.
- Automating chat management tasks based on chat properties.
Example:
You have an automation that triggers when a new message arrives, and you want to enrich the data with full chat details before processing or storing it. Using this node's Get Chat operation, you can retrieve the chat info by providing the chat ID.
Properties
Name | Meaning |
---|---|
Chat ID | The unique identifier of the chat to retrieve information for. Example: "122323". |
Output
The node outputs an array of JSON objects representing the response from the TelePilot API for the requested operation.
For the Get Chat operation, the output JSON contains detailed information about the specified chat, including but not limited to:
- Chat identifiers
- Chat type (private, group, supergroup, channel)
- Title or name of the chat
- Status and permissions
- Other metadata related to the chat
The exact structure depends on the Telegram API response but generally includes all relevant chat attributes.
If the node handles binary data (e.g., sending photos or videos), the binary output would represent the media content, but for Get Chat, the output is purely JSON.
Dependencies
- Requires an active Telegram API credential configured in n8n with appropriate API keys and authentication tokens.
- Depends on the TelePilot Node Connection Manager to manage Telegram client sessions and authentication states.
- 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" may occur. Resolve by re-authenticating using the login flow described at https://telepilot.co/login-howto.
- Unauthorized Errors: These indicate invalid or expired credentials. Reconnect or update your Telegram API credentials.
- Invalid Chat ID: Providing a wrong or non-existent chat ID will result in errors or empty responses. Verify the chat ID before use.
- Rate Limits or Network Issues: Temporary failures communicating with Telegram servers may happen; retry after some time.
- Command Not Supported: For other operations, ensure commands and parameters are valid per the node's documentation.
Links and References
- TelePilot Login Guide — Instructions for authenticating and managing Telegram sessions.
- Telegram Bot API Documentation — Official Telegram API reference (note: TelePilot uses TDLib internally, so some differences exist).
- n8n Documentation — General guidance on using custom nodes and credentials in n8n.