Actions12
Overview
This node enables forwarding a message from one Telegram chat to another using the Telegram Client API. It is useful when you want to programmatically share or duplicate messages across different chats or channels without manually copying and pasting content.
Common scenarios include:
- Automatically forwarding important announcements from a main channel to multiple group chats.
- Duplicating user queries or support messages to a dedicated support team chat.
- Archiving messages by forwarding them to a private chat or channel.
Example: Forward a message with ID 12345 from chat "@sourceChannel" to chat "-1009876543210".
Properties
| Name | Meaning |
|---|---|
| Chat ID | The source chat/channel ID or username where the original message exists (e.g., @username). |
| Message ID | The unique identifier of the message to forward. |
| To Chat ID | The destination chat ID or username where the message will be forwarded. |
| Options | Additional options (not used specifically in forwarding, but available for other operations). |
Output
The output JSON contains information about the forwarding operation:
success: Boolean indicating if the forwarding was successful.originalMessageId: The ID of the original message that was forwarded.forwardedMessages: An array containing details of the forwarded message(s) returned by the Telegram API.fromChatId: The source chat ID from which the message was forwarded.toChatId: The destination chat ID to which the message was forwarded.
No binary data is output by this operation.
Example output:
{
"success": true,
"originalMessageId": 12345,
"forwardedMessages": [ /* forwarded message objects */ ],
"fromChatId": "@sourceChannel",
"toChatId": "-1009876543210"
}
Dependencies
- Requires an active Telegram Client API credential with valid session, API ID, and API hash.
- The node uses the Telegram Client SDK internally to connect and perform actions.
- Network connectivity to Telegram servers is required.
- No additional environment variables are needed beyond the configured credentials.
Troubleshooting
- No credentials provided: Ensure the Telegram Client API credentials are set up correctly in n8n before running the node.
- Operation not supported error: Verify that the selected operation is "Forward Message" and all required parameters are provided.
- Invalid chat or message ID: Confirm that the chat IDs and message ID exist and are accessible by the authenticated Telegram client.
- Connection issues: Check network connectivity and Telegram API availability.
- Permission errors: The bot or client must have permission to read messages in the source chat and send messages in the destination chat.
If the node is set to continue on fail, errors will be returned in the output JSON under the error field.