Actions32
- Bot Actions
- Callback Actions
- Chat Actions
- File Actions
- Message Actions
- Payment Actions
- Sticker Actions
Overview
The "Copy Message" operation of the BaleMessenger node allows users to copy a message from one chat to another within the Bale Messenger platform. This is useful when you want to duplicate or repost content without manually forwarding or recreating it. For example, you might use this to replicate announcements across multiple group chats or to archive messages by copying them into a dedicated chat.
In practice, you specify the source chat and message ID, as well as the target chat where the message should be copied. The node then performs the copy action via the Bale Messenger API.
Properties
| Name | Meaning |
|---|---|
| Chat ID | Unique identifier for the target chat where the message will be copied to. |
| From Chat ID | Unique identifier for the chat where the original message was sent (source chat). |
| Message ID | Unique identifier of the message to copy from the source chat. |
Output
The output JSON contains:
messageId: The identifier of the newly copied message in the target chat.
This confirms that the message has been successfully copied and provides the new message's ID for further reference or actions.
No binary data is output by this operation.
Dependencies
- Requires an active Bale Messenger API authentication token configured in n8n credentials.
- Uses the official Bale Messenger Bot API endpoint (
https://tapi.bale.ai/bot). - Relies on the
node-telegram-bot-apilibrary internally for API communication.
Troubleshooting
Common Issues:
- Invalid or missing chat IDs or message IDs can cause failures.
- Insufficient permissions for the bot in either the source or target chat may prevent copying.
- Network or API errors from the Bale Messenger service.
Error Messages:
- Errors related to invalid identifiers typically indicate incorrect input parameters.
- Permission-related errors suggest the bot needs appropriate rights in the involved chats.
- API request failures may include HTTP error details; checking the API token validity and network connectivity is recommended.
To resolve issues, verify all IDs are correct, ensure the bot has necessary permissions, and confirm the API token is valid and active.
Links and References
- Bale Messenger Bot API Documentation (official API docs)
- n8n Documentation (for general node usage and credential setup)