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 interact with its CRM and business resources. The "Delete Entity" operation under the "Data Storage" resource enables users to delete a specified entity by its ID from Bitrix24.
Common scenarios for this node include:
- Automating cleanup of outdated or irrelevant CRM records.
- Removing test or duplicate entities during data synchronization workflows.
- Managing lifecycle events where entities need to be programmatically deleted based on external triggers.
For example, a user might configure this node to delete a contact or deal in Bitrix24 when it is marked as inactive in another system, ensuring data consistency across platforms.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24. Options: OAuth2 (recommended), Webhook (simpler), API Key |
| Entity ID | The unique identifier of the entity to delete. This is a required string input. |
Output
The node outputs JSON data representing the result of the deletion operation. Typically, this will confirm whether the entity was successfully deleted or provide error details if the operation failed.
If an error occurs 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 produced by this operation.
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 operations.
- Proper configuration of credentials within n8n is necessary to authorize API calls.
Troubleshooting
Common Issues:
- Invalid or expired authentication credentials can cause authorization failures.
- Providing an incorrect or non-existent Entity ID will result in errors indicating the entity could not be found.
- Network connectivity issues may prevent successful API communication.
Error Messages:
- Errors returned from Bitrix24 API are surfaced in the node's output under the
errorfield if "Continue On Fail" is enabled. - Typical messages include authentication failures, permission denials, or invalid entity references.
- Errors returned from Bitrix24 API are surfaced in the node's output under the
Resolution Tips:
- Verify that the authentication method and credentials are correctly set up and have sufficient permissions.
- Double-check the Entity ID value for correctness.
- Ensure network access to Bitrix24 API endpoints is available.