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 integrates with the Bitrix24 platform, specifically allowing users to update comments on timeline entries within Bitrix24. It is useful in scenarios where automated workflows need to modify existing comments programmatically, such as updating status notes, correcting information, or appending additional details to a comment in a CRM timeline.
Practical examples include:
- Automatically updating a support ticket comment when its status changes.
- Modifying a sales lead comment based on new data from an external system.
- Correcting or enriching timeline comments after data validation or enrichment steps.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication. |
| Comment ID | The unique identifier of the comment to update. |
| Comment Data | JSON-formatted data representing the updated content and properties of the comment. |
| Options | Additional optional parameters including: |
| - Filter | JSON object specifying filter criteria (not typically used for update operation). |
| - Order | JSON object specifying sort order (not typically used for update operation). |
| - Start | Number indicating start position for pagination (not typically used for update operation). |
Output
The node outputs an array containing one item per input, each with a json property holding the response from Bitrix24 after attempting to update the comment. The structure generally includes the updated comment data or an error message if the update failed.
If an error occurs and "Continue On Fail" is enabled, the output will contain an error object with fields:
error: The error message string.resource: The resource name ("timeline").timestamp: ISO timestamp of the error occurrence.
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.
- Network access to Bitrix24 API endpoints is required.
Troubleshooting
Common Issues:
- Invalid or expired authentication credentials causing authorization failures.
- Incorrect or missing Comment ID leading to "comment not found" errors.
- Malformed JSON in the Comment Data property causing request failures.
- Insufficient permissions in Bitrix24 account to update timeline comments.
Error Messages:
- Errors returned by Bitrix24 API are passed through; typical messages include authentication errors, invalid parameters, or permission denials.
- If "Continue On Fail" is enabled, errors are returned in the output JSON for easier debugging without stopping workflow execution.
Resolutions:
- Verify and refresh authentication credentials.
- Ensure the Comment ID exists and is correct.
- Validate JSON syntax in Comment Data before running the node.
- Confirm user permissions in Bitrix24 allow comment updates.