BaleMessenger icon

BaleMessenger

Interact with Bale Messenger API

Actions32

Overview

The node integrates with the Bale Messenger API to send various types of messages and perform chat-related actions. Specifically, for the Message resource and Send Video operation, it allows sending video files to a specified chat either by uploading binary data or by referencing an existing file on Bale servers.

This node is useful in scenarios where automated workflows need to share video content directly within Bale Messenger chats, such as sending promotional videos, tutorials, or user-generated content.

Example use cases:

  • Automatically sending a welcome video to new users joining a chat.
  • Sharing recorded event highlights or announcements via video.
  • Broadcasting product demo videos to customer support groups.

Properties

Name Meaning
Chat ID Unique identifier for the target chat where the video will be sent.
Binary Data Boolean flag indicating whether the video data should be taken from a binary field in the input data (true) or referenced by a file ID already stored on Bale servers (false).
Binary Property The name of the binary property containing the video data to upload when Binary Data is true.
File ID Identifier of a video file that already exists on Bale servers to send without uploading new data (used when Binary Data is false).
Caption Optional text caption to accompany the video message (0-1024 characters).
Reply Markup Additional interface options for the message, including:
- Inline Keyboard
- Reply Keyboard
- Reply Keyboard Remove
- None (no additional markup)
Inline Keyboard Configuration for inline keyboard buttons displayed next to the message (if Reply Markup is set to Inline Keyboard). Allows adding multiple rows and buttons with callback data or URLs.
Reply Keyboard Configuration for a custom reply keyboard with buttons (if Reply Markup is set to Reply Keyboard). Supports multiple rows of buttons with text labels.
Reply Keyboard Remove Options to remove a custom reply keyboard from the client (if Reply Markup is set to Reply Keyboard Remove). Includes flags to remove keyboard selectively or for all users.
Reply To Message ID If the video message is a reply, this is the ID of the original message being replied to.
File Name Optional filename for the uploaded video when using binary data. Helps specify the file extension and name (e.g., "video.mp4").

Output

The node outputs JSON data representing the response from the Bale Messenger API after sending the video message. This typically includes details about the sent message such as message ID, chat ID, date, and video metadata.

No binary output is produced by this operation since the node only sends video data but does not download or return video content.

Example output structure (simplified):

{
  "message_id": 12345,
  "chat": {
    "id": "chatId",
    "type": "group"
  },
  "date": 1610000000,
  "video": {
    "file_id": "abc123",
    "width": 640,
    "height": 480,
    "duration": 30,
    "mime_type": "video/mp4"
  },
  "caption": "Optional caption text"
}

Dependencies

  • Requires an active Bale Messenger API token credential configured in n8n.
  • Uses the official Bale Messenger Bot API endpoint (https://tapi.bale.ai/bot).
  • Relies on the node-telegram-bot-api library internally for API calls.
  • For sending binary video data, the input must include the video file in a binary property matching the configured Binary Property name.

Troubleshooting

  • Invalid Chat ID: Ensure the Chat ID is correct and the bot has permission to send messages to that chat.
  • File Not Found: When using File ID, verify the file exists on Bale servers and the ID is valid.
  • Binary Data Issues: If Binary Data is true, confirm the binary property contains valid video data and the filename has an appropriate extension.
  • Caption Too Long: Captions must be between 0 and 1024 characters; exceeding this limit may cause errors.
  • Reply Markup Misconfiguration: Incorrectly structured inline or reply keyboards can cause API errors. Validate button configurations carefully.
  • API Authentication Errors: Check that the Bale Messenger API token credential is correctly set up and has not expired or been revoked.

Common error messages usually come from the Bale API and indicate issues like invalid parameters, unauthorized access, or malformed requests. Reviewing the error details returned by the API helps pinpoint the problem.

Links and References

Discussion