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 details about a timeline note by its ID. The "Get Note" operation under the "Timeline" resource fetches information about a specific note in the Bitrix24 timeline, which is useful for workflows that need to access or process historical notes related to CRM entities or activities.
Common scenarios include:
- Automating retrieval of timeline notes for auditing or reporting.
- Integrating Bitrix24 timeline data into other systems or dashboards.
- Triggering further actions based on the content or metadata of a timeline note.
Example: A workflow that, upon receiving a note ID, fetches the note's details and sends a summary email to a team member.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication. |
| Note ID | The unique identifier of the timeline note to retrieve. |
| Options | Additional optional parameters: |
| - Filter | JSON-formatted filter criteria to refine the request (usage depends on API support). |
| - Order | JSON-formatted sort order specification (usage depends on API support). |
| - Start | Numeric start position for pagination (if applicable). |
Output
The node outputs an array of items where each item contains a json object representing the retrieved timeline note's data. This typically includes all fields returned by the Bitrix24 API for the note, such as note content, creation date, author, and any associated metadata.
If an error occurs and the node is configured to continue on failure, the output will contain an item with an error field describing the issue, along with the resource name and a timestamp.
The node does not output binary data.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods:
- OAuth2 authentication (recommended for production use).
- Webhook URL authentication (simpler but less secure).
- API key authentication.
- Proper credentials must be configured in n8n for the chosen authentication method.
- Access to the Bitrix24 API endpoint that supports timeline note retrieval.
Troubleshooting
Common issues:
- Invalid or missing Note ID: Ensure the Note ID provided exists and is correct.
- Authentication failures: Verify that the selected authentication method is correctly configured and valid.
- API rate limits or permission errors from Bitrix24: Check API usage quotas and user permissions.
Error messages:
- Errors thrown by the Bitrix24 API will be surfaced in the node's output if "Continue On Fail" is enabled.
- Typical error messages may include "Note not found", "Unauthorized", or "Invalid authentication".
Resolution tips:
- Double-check Note ID input.
- Confirm credentials and authentication settings.
- Review Bitrix24 API documentation for required permissions.
- Enable "Continue On Fail" to capture error details without stopping workflow execution.