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 properties of entity items within Bitrix24's data storage. It is useful for automating updates to CRM entities such as contacts, deals, leads, companies, and custom Smart Process Automation (SPA) entities.
Typical use cases include:
- Updating a specific property of a CRM entity item when certain conditions are met in a workflow.
- Automating changes to entity fields based on external triggers or data inputs.
- Managing custom properties of entities programmatically without manual intervention.
For example, you might use this node to update the "Status" property of a deal entity after receiving new information from an external system, or to modify a contact's custom field based on user input collected elsewhere.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key. |
| Property ID | The unique identifier of the entity item property to update. |
| Property Name | The name of the entity item property being updated. |
| Property Code | The code representing the entity item property. |
| Property Type | The type of the property. Possible values: String, Number, List, File, Date, DateTime, HTML, Element, GPS, User. |
| Property Required | Boolean indicating whether the property is required. |
| Property Sort Order | Numeric value defining the sort order of the property. |
| Property Multiple | Boolean indicating if the property can hold multiple values. |
| Property Active | Boolean indicating if the property is active. |
| Property Values | For list-type properties, a collection containing a comma-separated list of possible values. |
Output
The node outputs JSON data representing the result of the update operation on the entity item property. This typically includes confirmation of the update or details about the updated property.
If the operation fails and "Continue On Fail" is enabled, the output will contain an error object with the error message, resource name, and timestamp.
No binary data output is indicated by the source code.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods: OAuth2, Webhook URL, or API Key.
- Needs proper configuration of credentials in n8n corresponding to the chosen authentication method.
- Relies on Bitrix24 API endpoints to perform operations on CRM and business platform entities.
- Uses internal helper functions to make standardized API calls to Bitrix24.
Troubleshooting
Common Issues:
- Authentication failures due to incorrect or expired credentials.
- Invalid property IDs or codes leading to API errors.
- Attempting to update inactive or non-existent properties.
- Network connectivity issues affecting API calls.
Error Messages:
- Errors returned from Bitrix24 API will be surfaced in the node output if "Continue On Fail" is enabled.
- Typical messages may include authorization errors, invalid parameter errors, or resource not found.
Resolutions:
- Verify that the selected authentication method is correctly configured and valid.
- Double-check property identifiers and ensure they exist and are active in Bitrix24.
- Ensure network access to Bitrix24 API endpoints.
- Use the node’s error output to diagnose and adjust parameters accordingly.