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 Bitrix24's Lists resource to update an existing element within a specified list. It allows users to modify fields of a list element by specifying the list ID, element ID, and the fields to update. This is useful in scenarios where you need to programmatically update records or items stored in Bitrix24 lists, such as updating customer information, task details, or any custom data stored in Bitrix24 lists.
Practical examples include:
- Updating a contact's details in a CRM list after receiving new information.
- Modifying task status or priority in a project management list.
- Changing inventory item attributes in a product list.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: OAuth2, Webhook, or API Key. |
| List ID | The unique identifier of the Bitrix24 list containing the element to update. |
| Element ID | The unique identifier of the element within the list that needs to be updated. |
| Fields | Collection of field name-value pairs representing the fields to update on the element. |
| Options | Additional optional parameters: - Access Token: Override the default access token. - Filter: JSON filter criteria. - Order: JSON sort order. - Select: Comma-separated list of fields to select. |
Output
The node outputs an array of JSON objects representing the response from Bitrix24 after attempting to update the element. Each output item contains the updated element data or error information if the update failed.
If the update is successful, the json output will typically include the updated element's fields and their new values as returned by Bitrix24.
Binary data output is not indicated for this operation.
Dependencies
- Requires valid Bitrix24 credentials configured in n8n, supporting OAuth2, webhook URL, or API key authentication.
- Network access to Bitrix24 API endpoints.
- Proper permissions in Bitrix24 to update list elements.
Troubleshooting
Common Issues:
- Invalid or missing List ID or Element ID will cause the update to fail.
- Incorrect field names or unsupported field values may result in errors.
- Insufficient permissions or expired/invalid authentication tokens can block updates.
- Malformed JSON in the "Filter" or "Order" options may cause request failures.
Error Messages:
- Errors returned from Bitrix24 API are passed through; typical messages include authorization errors, invalid IDs, or validation errors on fields.
- If the node is set to continue on failure, errors are included in the output JSON under an
errorproperty with a timestamp.
Resolution Tips:
- Verify that List ID and Element ID are correct and exist in Bitrix24.
- Ensure the authentication method is properly configured and tokens are valid.
- Double-check field names and values against Bitrix24 list schema.
- Validate JSON syntax in optional filter/order parameters.