Actions32
- Bot Actions
- Callback Actions
- Chat Actions
- File Actions
- Message Actions
- Payment Actions
- Sticker Actions
Overview
The "Forward Message" operation in the BaleMessenger node allows users to forward a message from one chat to another within the Bale Messenger platform. This is useful when you want to share content originally sent in one chat with participants of another chat without manually copying and pasting the message content.
Common scenarios include:
- Automatically forwarding important announcements or alerts from a source chat to multiple target chats.
- Sharing user-generated content or feedback received in one chat to a support or admin chat.
- Relaying messages between different groups or channels for broader dissemination.
Example: Forward a message with ID 12345
from chat A
to chat B
, so all members of chat B
receive the original message as if it was sent there directly.
Properties
Name | Meaning |
---|---|
Chat ID | Unique identifier for the target chat where the message will be forwarded 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 forward. |
Output
The output JSON contains a field named res
which holds the response from the Bale Messenger API after attempting to forward the message. This typically includes confirmation details about the forwarded message, such as its new message ID or status.
No binary data is output by this operation.
Example output structure:
{
"res": {
// API response details about the forwarded message
}
}
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
) to perform the forwarding action. - No additional external services are required beyond the Bale Messenger API.
Troubleshooting
- Invalid Chat ID or From Chat ID: If either chat identifier is incorrect or the bot does not have access to the specified chats, the forwarding will fail. Verify that the chat IDs are correct and the bot is a member or admin in those chats.
- Invalid Message ID: The message to forward must exist in the source chat. Ensure the message ID is valid and accessible.
- API Authentication Errors: If the API token is missing, expired, or invalid, requests will fail. Check the configured API credentials.
- Permission Issues: The bot must have permission to read messages in the source chat and send messages in the target chat.
- Error Messages: The node may return error details in the output JSON under
errorMessage
or similar fields if forwarding fails. Review these messages for clues on resolution.
Links and References
- Bale Messenger Bot API Documentation (official API docs)
- n8n Documentation - Creating Custom Nodes
- Telegram Bot API (similar concepts) — Bale Messenger API is inspired by Telegram's API design.