Actions32
- Bot Actions
- Callback Actions
- Chat Actions
- File Actions
- Message Actions
- Payment Actions
- Sticker Actions
Overview
This node interacts with the Bale Messenger API, specifically providing functionality to retrieve information about files stored on Bale servers when using the "File" resource with the "Get File" operation. It allows users to fetch detailed metadata about a file by supplying its unique file ID.
Common scenarios include:
- Retrieving file details such as file path, size, or other metadata for further processing or downloading.
- Integrating Bale Messenger file management into automated workflows.
- Using file information to reference or share files within chatbots or messaging automation.
Practical example:
- A workflow that receives a file ID from a previous step (e.g., a message containing a file) and uses this node to get the file's download URL or metadata for archiving or forwarding.
Properties
| Name | Meaning |
|---|---|
| File ID | The unique identifier of the file on Bale servers. Required to specify which file to retrieve. |
Output
The node outputs a JSON object containing the file details returned by the Bale Messenger API. This typically includes metadata such as:
file_id: The unique identifier of the file.file_size: Size of the file in bytes.file_path: Path to the file on Bale servers, which can be used to download the file.
No binary data is output by this operation; it only returns JSON metadata about the file.
Dependencies
- Requires an active Bale Messenger API credential with a valid authentication token.
- Uses the official Bale Messenger API endpoint (
https://tapi.bale.ai/bot). - The node depends on the
node-telegram-bot-apilibrary configured to use Bale's API base URL. - No additional environment variables are required beyond the API credentials.
Troubleshooting
- Invalid or missing File ID: Ensure the
File IDproperty is correctly set and corresponds to an existing file on Bale servers. - Authentication errors: Verify that the provided API token credential is valid and has necessary permissions.
- Network issues: Check connectivity to the Bale Messenger API endpoint.
- API errors: If the API returns an error, inspect the error message for details such as file not found or permission denied.
If the node throws errors related to the API response, reviewing the exact error message and ensuring correct input parameters usually resolves the issue.
Links and References
- Bale Messenger API Documentation (general reference for Bale Messenger API)
- Bale Messenger Bot API (API base URL used by the node)
This summary focuses exclusively on the "File" resource with the "Get File" operation as requested.