Actions32
- Bot Actions
- Callback Actions
- Chat Actions
- File Actions
- Message Actions
- Payment Actions
- Sticker Actions
Overview
The node interacts with the Bale Messenger API to perform various messaging-related actions. Specifically, for the Message resource and the Forward Message operation, it forwards a message from one chat to another. This is useful when you want to share or relay messages between different chats or groups without manually copying and pasting content.
Practical scenarios include:
- Automatically forwarding important announcements from a main channel to multiple group chats.
- Relaying user queries or feedback from one chat to a support team chat.
- Archiving messages by forwarding them to a dedicated chat for record-keeping.
Properties
| Name | Meaning |
|---|---|
| Chat ID | Unique identifier for the target chat where the message will be forwarded to. |
| From Chat ID | Unique identifier of the chat where the original message was sent (source chat). |
| Message ID | Unique identifier of the message to forward. |
These properties are required to specify which message to forward and where to forward it.
Output
The output JSON contains a field named res which holds the response from the Bale Messenger API after attempting to forward the message. The exact structure depends on the API but generally includes confirmation details about the forwarded message.
Example output snippet:
{
"res": {
// API response data confirming the forwarded message
}
}
No binary data output is involved in 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). - No additional external services or environment variables are needed beyond the API credential.
Troubleshooting
- Invalid Chat ID or From Chat ID: Ensure that both chat identifiers are correct and accessible by the bot; otherwise, the API call will fail.
- Invalid Message ID: The message to forward must exist in the source chat; if not, the operation will error out.
- API Authentication Errors: Verify that the API token credential is valid and has sufficient permissions.
- Network Issues: Connectivity problems can cause request failures; check network access to the Bale Messenger API endpoint.
- Error Handling: The node captures errors from the API and returns them in the output JSON under
errorMessageanderrorDetailsfields if forwarding fails.
Links and References
- Bale Messenger Bot API Documentation (official API docs)
- n8n Documentation (for general node usage and credential setup)