Actions26
- Chat Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
The node "Telegram CoPilot" integrates with the Telegram API to perform various Telegram-related actions programmatically. Specifically, for the Message resource and Forward Messages operation, it forwards one or more messages from a source chat to a target chat.
This node is useful in scenarios where you want to automate message forwarding between chats on Telegram without manual intervention. For example:
- Automatically forwarding important alerts or notifications from a monitored group chat to a private chat.
- Duplicating messages from one channel or group to another for archiving or broadcasting purposes.
- Creating bots that relay messages between different Telegram chats based on custom logic.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The identifier of the destination chat where the messages will be forwarded. |
| From Chat ID | The identifier of the source chat from which the messages will be forwarded. |
| Message IDs | Comma-separated list of message identifiers to forward from the source chat to the target. |
Output
The output is a JSON array containing the result(s) of the forwarding operation. Each element corresponds to the response from the Telegram API for the forwarded messages. The structure typically includes details about the forwarded messages such as their new message IDs, timestamps, and metadata returned by Telegram.
No binary data output is indicated for this operation.
Dependencies
- Requires an active Telegram API authentication credential (an API key and associated login).
- Uses a connection manager to handle Telegram client sessions.
- The node depends on the Telegram TDLib-based API via the TelePilot library.
- Proper login/authentication must be established before forwarding messages; otherwise, errors related to unauthorized access or closed sessions occur.
Troubleshooting
Common Issues:
- Forwarding fails if the Telegram session is not logged in or has expired.
- Invalid or missing chat IDs or message IDs can cause errors.
- Network issues or Telegram API rate limits may interrupt forwarding.
Error Messages:
"Session was closed or terminated. Please login again": Indicates the Telegram client session is no longer valid. Solution: Re-authenticate using the login flow."Please login": The node attempted an operation without a valid authenticated session. Solution: Use the login operation first.- Errors related to invalid message or chat IDs usually mean the provided IDs do not exist or are inaccessible by the authenticated user.
Links and References
- TelePilot Login Guide — Instructions for authenticating your Telegram account.
- Telegram TDLib Documentation: https://core.telegram.org/tdlib
- Telegram Bot API Overview: https://core.telegram.org/bots/api