Actions27
- Chat Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
This node, named "Telegram CoPilot," provides extensive integration with the Telegram messaging platform via a personal Telegram client session. It allows users to perform a wide range of Telegram operations programmatically within n8n workflows. The node supports managing user login sessions, sending and editing messages, handling chats and groups, managing contacts, and working with files.
The "Send Viseo" operation under the "Message" resource specifically enables sending video messages to a Telegram chat by providing a video URL and optional reply message ID.
Common scenarios where this node is beneficial include automating Telegram messaging for customer support, broadcasting updates, managing group chats, or integrating Telegram interactions into broader automation workflows.
Example use case: Automatically send a promotional video to a specific Telegram chat when a new product is launched.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The unique identifier of the Telegram chat where the message or action will be performed. |
For the "Send Viseo" operation (under "Message" resource), additional input properties used internally but not listed in your provided JSON are:
- VideoUrl: The URL of the video to send.
- reply_to_msg_id: Optional message ID to which the video message replies.
These are inferred from the code but were not included in your property list.
Output
The node outputs an array of JSON objects representing the result of the invoked Telegram API call. For the "Send Viseo" operation, the output JSON contains details about the sent video message, including metadata such as message ID, chat ID, content type, and status.
If the operation involves binary data (e.g., sending photos or videos), the node handles the file upload via local paths or remote URLs, but the output remains JSON describing the message sent rather than raw binary data.
Dependencies
- Requires a valid Telegram API authentication credential (an API key credential with apiId, apiHash, and phoneNumber).
- Depends on the TelePilot library and its connection manager to handle Telegram client sessions.
- Requires proper login and session management; users must authenticate their Telegram account before performing most operations.
- The node uses the Telegram TDLib API under the hood.
Troubleshooting
- Session Not Logged In: If the Telegram account is not logged in, the node throws errors prompting the user to log in using the ChatTrigger node and follow the login guide at https://telepilot.co/login-howto.
- Closed Client Error: Errors like "A closed client cannot be reused" indicate that the session was terminated; the user should re-authenticate.
- Unauthorized Error: Indicates invalid or expired credentials; requires re-login.
- Invalid Chat ID or Message ID: Operations requiring chat or message IDs will fail if these are incorrect or missing.
- Command Not Supported: When using login commands, unsupported commands return guidance messages.
- Users should ensure all required parameters are provided and correctly formatted (e.g., comma-separated lists for multiple IDs).