BaleMessenger icon

BaleMessenger

Interact with Bale Messenger API
Join our community

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 workflows.
  • Validating chat existence or properties before performing further actions.

Example: You have a workflow that triggers on certain events and needs to get the current state or info of a chat (e.g., group or channel) before deciding what message to send next.

Properties

Name Meaning
Chat ID Unique identifier for the target chat. Required to specify which chat's information to get.

Output

The output JSON contains the detailed information about the requested chat as returned by the Bale Messenger API. 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 JSON snippet:

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

Dependencies

  • Requires an active Bale Messenger API credential with a valid token.
  • Uses the Bale Messenger API endpoint https://tapi.bale.ai/bot to make requests.
  • The node depends on the official Bale Messenger API client library internally.

Troubleshooting

  • Invalid Chat ID: If the provided Chat ID does not exist or is incorrect, the API may return an error or empty response. Verify the Chat ID is correct.
  • Authentication Errors: Ensure the API token credential is valid and has permissions to access chat information.
  • Network Issues: Connectivity problems to the Bale Messenger API endpoint can cause failures; check network and proxy settings.
  • API Rate Limits: Excessive requests might be throttled by the API; implement retry logic or reduce request frequency.

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

Links and References

Discussion