Actions290
- Task Actions
- Direct API Actions
- CRM Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Get Entity
- Add Entity
- Update Entity
- Delete Entity
- Get Entity Rights
- Get Entity Sections
- Add Entity Section
- Update Entity Section
- Delete Entity Section
- Get Entity Item
- Add Entity Item
- Update Entity Item
- Delete Entity Item
- Get Entity Item Properties
- Add Entity Item Property
- Update Entity Item Property
- Delete Entity Item Property
- Chat Actions
- User Field Actions
- File Actions
- User Field Config Actions
- Duplicate Actions
- Timeline Actions
- Disk Actions
- Upload File
- Download File
- Delete File
- Get File Info
- List Files
- Create Folder
- Delete Folder
- Get Storage Info
- Get Storages
- Get Storage
- Get Folders
- Get Folder
- Add Folder
- Update Folder
- Copy Folder
- Move Folder
- Rename Folder
- Get Files
- Get File
- Copy File
- Move File
- Rename File
- Share Item
- Get Shared Items
- Get Sharing Rights
- Update Sharing Rights
- Workflow Actions
- Status Actions
- Calendar Actions
- Chatbot Actions
- Events Actions
- Lists Actions
- Product Actions
- Open Lines Actions
- Telephony Actions
- Register External Call
- Finish External Call
- Hide External Call
- Show External Call
- Search CRM Entities
- Attach Call Record
- Get External Line
- Add External Line
- Update External Line
- Delete External Line
- Get Voximplant Statistics
- Get Voximplant Line
- Get Voximplant SIP Connector
- Get Voximplant SIP Line
- Add Voximplant SIP Line
- Update Voximplant SIP Line
- Delete Voximplant SIP Line
- Message Service Actions
- Notify Actions
Overview
This node interacts with the Bitrix24 platform, specifically allowing users to retrieve detailed information about a single timeline log message by its ID. The "Get Log Message" operation under the "Timeline" resource fetches a specific log entry from Bitrix24's activity timeline.
Common scenarios where this node is beneficial include:
- Auditing or reviewing specific events or actions recorded in Bitrix24.
- Fetching detailed logs for troubleshooting or compliance purposes.
- Integrating Bitrix24 timeline data into external reporting or monitoring systems.
For example, a user might want to automatically retrieve and analyze a particular log message related to a CRM deal update or a system notification stored in Bitrix24's timeline.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key authentication |
| Log Message ID | The unique identifier of the log message to retrieve. This is required to specify which timeline entry to get. |
| Options | Additional optional parameters: - Filter: JSON object specifying filter criteria (not typically used for single log retrieval) - Order: JSON object specifying sort order (not typically used here) - Start: Number indicating pagination start position (not typically used here) |
Output
The node outputs an array of items, each containing a json property with the retrieved log message data from Bitrix24. The structure of the json output corresponds to the fields returned by the Bitrix24 API for a timeline log message, including details such as message content, timestamps, author, and related entities.
If an error occurs and "Continue On Fail" is enabled, the output will contain an item with an error field describing the issue, along with the resource name and a timestamp.
No binary data output is indicated for this operation.
Dependencies
Requires valid authentication credentials for Bitrix24, which can be provided via:
- OAuth2 token
- Webhook URL
- API key
The node depends on Bitrix24's REST API endpoints to fetch timeline log messages.
No additional external services are required beyond Bitrix24 itself.
Troubleshooting
Common Issues:
- Invalid or missing Log Message ID will cause the API call to fail.
- Incorrect or expired authentication credentials will result in authorization errors.
- Network connectivity issues may prevent successful API calls.
Error Messages:
- Errors thrown by the node will include the error message from Bitrix24's API.
- If "Continue On Fail" is enabled, errors are returned in the output JSON with an
errorfield.
Resolutions:
- Verify that the Log Message ID is correct and exists in the Bitrix24 account.
- Ensure authentication credentials are valid and have sufficient permissions.
- Check network connectivity and Bitrix24 service status.