BaleMessenger icon

BaleMessenger

Interact with Bale Messenger API

Actions32

Overview

The node interacts with the Bale Messenger API to perform various chat-related operations. Specifically, for the Chat resource and Get Chat operation, it retrieves up-to-date information about a specific chat by its unique identifier. This is useful when you want to fetch details such as chat type, title, description, or other metadata related to a chat in Bale Messenger.

Common scenarios include:

  • Monitoring chat details before sending messages.
  • Fetching chat info to display or log in your workflow.
  • Validating chat existence or properties before performing further actions.

Example: You have a chat ID from an incoming message and want to get the chat's current title and member count before sending a notification.

Properties

Name Meaning
Chat ID Unique identifier for the target chat whose information you want to retrieve (string).

Output

The output JSON contains the detailed information of the requested chat as returned by the Bale Messenger API's getChat method. The structure typically includes fields such as chat ID, type, title, username, description, and other relevant metadata describing the chat.

No binary data is output for this operation.

Example output snippet (fields may vary):

{
  "id": 123456789,
  "type": "group",
  "title": "My Group Chat",
  "username": "mygroupchat",
  "description": "This is a group chat for project discussion"
}

Dependencies

  • Requires an active Bale Messenger API credential with a valid token configured in n8n.
  • Uses the official Bale Messenger API endpoint at https://tapi.bale.ai/bot.
  • Depends on the node-telegram-bot-api library internally adapted for Bale Messenger API calls.
  • No additional environment variables are required beyond the API credential.

Troubleshooting

  • Invalid Chat ID: If the provided chat ID does not exist or is incorrect, the API call will fail. Verify the chat ID is correct and that the bot has access to the chat.
  • Authentication Errors: Ensure the API token credential is valid and has sufficient permissions.
  • Network Issues: Connectivity problems to the Bale Messenger API endpoint can cause failures; check network access.
  • API Rate Limits: Excessive requests might be throttled by the API; implement retries or delays if needed.

Error messages from the API are logged and included in the node output under error fields if the request fails.

Links and References

Discussion