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
The node integrates with the Bitrix24 platform, specifically enabling interaction with its CRM and business resources. The "Data Storage" resource's "Update Entity Item" operation allows users to update a specific item within an entity in Bitrix24. This is useful for automating updates to CRM records such as contacts, deals, or custom entities.
Typical use cases include:
- Automatically updating customer information when new data arrives.
- Modifying deal stages or statuses based on external triggers.
- Adjusting custom entity items' properties dynamically during workflows.
For example, you might update a contact's phone number or change a deal's status after receiving payment confirmation.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook URL (simpler), or API Key |
| Entity ID | The unique identifier of the entity containing the item to update |
| Item ID | The unique identifier of the specific item within the entity to update |
| Item Name | The name of the entity item |
| Item Active | Boolean flag indicating whether the item is active |
| Item Sort Order | Numeric value defining the sort order of the item |
| Item Description | Text description of the item |
| Item Properties | Collection of additional property values for the item, provided as JSON |
Output
The node outputs an array of items where each item contains a json object representing the updated entity item data returned from Bitrix24. This typically includes all fields of the updated item as stored in Bitrix24.
If the operation fails but "Continue On Fail" is enabled, the output will contain an error object with:
error: The error message string.resource: The resource name ("data storage" or equivalent).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 token (recommended for production).
- Bitrix24 webhook URL.
- Bitrix24 API key.
- The node depends on Bitrix24 API endpoints to perform entity item updates.
- Proper credentials must be configured in n8n for the chosen authentication method.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials causing authorization failures.
- Incorrect Entity ID or Item ID leading to "item not found" errors.
- Malformed JSON in "Item Properties" causing request failures.
- Insufficient permissions on Bitrix24 side to update the specified entity/item.
Error messages:
- Authorization errors: Check that the API key, OAuth token, or webhook URL is valid and has required scopes.
- Not found errors: Verify that the Entity ID and Item ID are correct and exist in Bitrix24.
- Validation errors: Ensure that required fields are provided and JSON syntax in properties is correct.
Enabling "Continue On Fail" allows workflow execution to proceed despite errors, returning error details in output.