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 operations on various resources such as CRM entities and timeline comments. The "Timeline - Delete Comment" operation enables users to delete a specific comment from the Bitrix24 timeline by providing its unique comment ID.
Common scenarios for this node include automating cleanup of timeline comments, managing user feedback or notes programmatically, or integrating Bitrix24 timeline comment management into broader workflows.
For example, you might use this node to automatically remove outdated or irrelevant comments from a deal's timeline after certain conditions are met, helping keep your CRM data clean and relevant.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key authentication. |
| Comment ID | The unique identifier of the comment to be deleted. |
| Options | Additional optional parameters: β’ Filter: JSON object specifying filter criteria (not typically used in delete). β’ Order: JSON object specifying sort order. β’ Start: Number indicating start position for pagination. |
Output
The node outputs an array of items corresponding to the result of the delete operation. Each item contains a json field with the response from Bitrix24 API.
- On success, the output typically confirms deletion (often an empty or success status).
- On failure, if "Continue On Fail" is enabled, the output includes an error message with fields:
error: The error message string.resource: The resource name ("timeline").timestamp: ISO timestamp of when the error occurred.
No binary data output is involved in this operation.
Dependencies
- Requires valid Bitrix24 credentials configured in n8n:
- An API key credential, or
- OAuth2 authentication, or
- A webhook URL.
- The node uses Bitrix24 REST API endpoints internally to perform actions.
- No additional external dependencies beyond Bitrix24 API access.
Troubleshooting
Common issues:
- Invalid or missing Comment ID will cause the API call to fail.
- Incorrect or expired authentication credentials will lead to authorization errors.
- Insufficient permissions in Bitrix24 to delete timeline comments.
- Network connectivity issues preventing API calls.
Error messages:
"error": "Comment not found"β Verify the Comment ID is correct and exists.- Authorization errors β Check that the provided authentication method and credentials are valid and have required scopes.
- Rate limiting or API quota exceeded β Wait and retry later or check Bitrix24 API limits.
Resolution tips:
- Double-check the Comment ID input.
- Ensure the selected authentication method matches your Bitrix24 setup.
- Enable "Continue On Fail" in the node settings to handle errors gracefully in workflows.