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 allows users to interact with the Bitrix24 platform, specifically to manage timeline notes among other resources. The "Delete Note" operation under the "Timeline" resource enables the deletion of a specific note by its ID from the Bitrix24 timeline. This is useful in scenarios where you want to programmatically remove outdated or irrelevant notes from your Bitrix24 CRM or business platform timeline.
Practical examples include:
- Automatically cleaning up notes related to closed deals.
- Removing notes created by mistake or duplicates.
- Managing timeline data as part of an automated workflow for CRM maintenance.
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 note to delete from the timeline. |
| Options | Additional optional parameters: - Filter: JSON object to filter results (not typically used in delete). - Order: JSON object to specify sort order. - Start: Number indicating pagination start position. |
Output
The node outputs a JSON object representing the result of the delete operation. Typically, this will confirm whether the note was successfully deleted or provide error information if the operation failed.
If the operation fails and "Continue On Fail" is enabled, the output JSON will contain an error field with the error message, along with the resource name and a timestamp.
No binary data output is involved in this operation.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods: OAuth2, Webhook URL, or API Key.
- Proper credentials must be configured in n8n for the chosen authentication method.
- The node relies on Bitrix24's API endpoints to perform operations.
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 set up and credentials are valid.
- Insufficient permissions: The authenticated user or API key must have rights to delete timeline notes.
- Network or API errors: Temporary connectivity issues or Bitrix24 API downtime can cause failures.
Error Messages:
- Errors returned from Bitrix24 API will be included in the output JSON under the
errorfield if "Continue On Fail" is enabled. - Common messages might indicate invalid IDs, permission denied, or authentication errors.
- Errors returned from Bitrix24 API will be included in the output JSON under the
Resolution Steps:
- Double-check Note ID correctness.
- Re-authenticate or update credentials.
- Confirm user permissions in Bitrix24.
- Retry after some time if network/API issues occur.