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 enabling operations on its CRM and business resources. The "Data Storage" resource with the "Update Entity" operation allows users to update existing entities within Bitrix24, such as CRM records or custom entities.
Typical use cases include:
- Updating customer or contact information in a CRM system.
- Modifying details of deals, leads, or other business objects.
- Automating updates to entity metadata like descriptions, active status, or sort order based on workflow triggers.
For example, after receiving updated client data from a form submission, this node can update the corresponding Bitrix24 entity to keep records synchronized.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook URL, or API Key |
| Entity ID | The unique identifier of the entity to update |
| Entity Name | The name of the entity |
| Entity Code | The code associated with the entity |
| Entity Active | Boolean flag indicating whether the entity is active |
| Entity Sort Order | Numeric value defining the sort order of the entity |
| Entity Description | Text description providing additional details about the entity |
Output
The node outputs an array of items where each item contains a json object representing the updated entity's data returned by Bitrix24 after the update operation.
If an error occurs and the node is configured to continue on failure, the output will contain an item with an error field describing the issue, along with the resource name and a timestamp.
No binary data output is produced by this node.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods: OAuth2, webhook URL, or API key.
- The node depends on Bitrix24's API endpoints to perform entity updates.
- Proper configuration of credentials in n8n is necessary to authorize API calls.
Troubleshooting
Common Issues:
- Invalid or expired authentication credentials leading to authorization errors.
- Incorrect or missing Entity ID causing the update to fail because the target entity cannot be found.
- Insufficient permissions for the authenticated user to modify the specified entity.
- Network connectivity issues preventing communication with Bitrix24 API.
Error Messages:
- Errors thrown by the node will include the message from Bitrix24 API responses.
- If the node is set to continue on failure, errors are returned in the output JSON under the
errorproperty.
Resolutions:
- Verify that the authentication method and credentials are correctly set up and valid.
- Ensure the Entity ID corresponds to an existing entity in Bitrix24.
- Confirm that the authenticated user has the required permissions to update entities.
- Check network connectivity and firewall settings to allow outbound requests to Bitrix24.