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 interaction with its CRM and business resources. The "Delete Entity Item Property" operation under the "Data Storage" resource enables users to delete a specific property from an entity item within Bitrix24. This is useful for cleaning up or removing outdated or incorrect data fields associated with CRM entities such as contacts, deals, leads, companies, etc.
Practical scenarios include:
- Removing obsolete custom fields from CRM records.
- Cleaning up properties that are no longer relevant after a process change.
- Automating data hygiene by deleting unwanted properties from entity items.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication. |
| Property ID | The unique identifier of the entity item property to be deleted. This is required to specify which property to remove. |
Output
The node outputs JSON data representing the result of the deletion operation. Typically, this will confirm whether the property was successfully deleted or provide error information if the operation failed.
If the operation fails and the node is configured to continue on failure, the output JSON will contain an error field with the error message, along with the resource name and a timestamp.
No binary data output is indicated in the source code.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
- Relies on Bitrix24's API endpoints to perform operations.
- The node uses internal helper functions to make standardized API calls to Bitrix24.
- No additional external services beyond Bitrix24 are required.
Troubleshooting
Common Issues:
- Invalid or expired authentication credentials can cause authorization failures.
- Providing an incorrect or non-existent Property ID will result in errors indicating the property could not be found or deleted.
- Network connectivity issues may prevent successful API calls.
Error Messages:
- Errors returned from Bitrix24 API will be surfaced in the node's output under the
errorfield if "Continue On Fail" is enabled. - Common error messages might include authentication failures, invalid parameters, or permission denied errors.
- Errors returned from Bitrix24 API will be surfaced in the node's output under the
Resolutions:
- Verify that the authentication method and credentials are correctly configured and valid.
- Double-check the Property ID to ensure it corresponds to an existing property on the target entity.
- Ensure the user account has sufficient permissions to delete properties.
- Check network connectivity and Bitrix24 service status.