Actions33
- Chat Actions
- Custom Request Actions
- File Actions
- Group Actions
- Message Actions
- User Actions
Overview
The node implements a Telegram messaging interface called "Telegram CoPilot" that allows users to interact with Telegram chats and messages programmatically. Specifically, the Forward Messages operation under the Message resource enables forwarding one or more messages from one chat to another.
This operation is useful in scenarios such as:
- Automatically forwarding important messages from a monitored chat to a different chat or group.
- Creating message pipelines where content is relayed between multiple Telegram channels or groups.
- Archiving or backing up messages by forwarding them to a dedicated chat.
For example, you could forward selected messages from a customer support chat to a team lead's private chat for review.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The identifier of the target chat where the messages will be forwarded. |
| From Chat ID | The identifier of the source chat from which the messages are forwarded. |
| Message IDs | Comma-separated list of message identifiers to forward from the source chat. |
| Reply to threadID | Optional. If not zero, specifies the message thread ID within the target chat to reply in. |
Output
The output is an array of JSON objects representing the result of the forwarding operation. Each object corresponds to the response from the Telegram API for the forwarded messages, typically including details about the forwarded messages such as their new message IDs, timestamps, and status.
No binary data output is produced by this operation.
Dependencies
- Requires an active Telegram API authentication credential (an API key and phone number login).
- Depends on the TelePilotNodeConnectionManager to manage Telegram client sessions.
- Requires proper login/authentication via the Telegram API before performing operations.
- No additional external services beyond Telegram API are needed.
Troubleshooting
Error: Please login
Occurs if the Telegram session is not authenticated. Solution: Use the login flow with phone number and code via the ChatTrigger node or the login operation before forwarding messages.Session was closed or terminated
Indicates the Telegram client session has expired or been closed. Re-login is required.Invalid chat or message IDs
Forwarding will fail if the provided chat IDs or message IDs do not exist or are incorrect. Verify IDs carefully.Permission errors (e.g., CHAT_WRITE_FORBIDDEN)
The bot/user may lack permission to send messages to the target chat. Ensure the account has write access.Empty or malformed message IDs
Themessage_idsproperty must be a comma-separated string of valid message IDs without extra spaces or invalid characters.
Links and References
- Telegram Bot API Documentation (for general forwarding concepts)
- TelePilot Login Guide (for authentication instructions)
- TelePilot Official Website