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 CRM and business platform, allowing users to perform various operations on Bitrix24 resources. Specifically, for the Data Storage resource with the Delete Entity Item operation, it enables deleting a specific item from an entity in Bitrix24.
Typical use cases include:
- Automating cleanup of outdated or incorrect records in Bitrix24 entities.
- Integrating Bitrix24 data management into broader workflows where entity items need to be programmatically removed.
- Managing CRM data lifecycle by removing leads, contacts, deals, or custom entity items as part of automated processes.
For example, you might use this node to delete a contact record identified by its ID after a customer unsubscribes, or remove a deal item that was canceled.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
| Entity ID | The unique identifier of the entity from which the item will be deleted. |
| Item ID | The unique identifier of the specific item within the entity to delete. |
Output
The node outputs JSON data representing the result of the deletion operation. Typically, this will confirm whether the deletion was successful or provide error details if it failed.
If the node encounters an error during execution and "Continue On Fail" is enabled, it outputs a JSON object containing:
error: The error message describing what went wrong.resource: The resource name involved in the operation.timestamp: The ISO timestamp when the error occurred.
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).
- Needs proper configuration of these credentials in n8n prior to use.
- Relies on Bitrix24's REST API endpoints to perform entity item deletions.
Troubleshooting
Common Issues
- Invalid or expired authentication: Ensure your OAuth2 token, webhook URL, or API key is valid and has sufficient permissions.
- Incorrect Entity ID or Item ID: Double-check that the IDs provided correspond to existing entities and items in Bitrix24.
- API rate limits or connectivity issues: Bitrix24 may throttle requests; verify network connectivity and consider retry logic.
Common Error Messages
"Failed to load CRM fields"or similar messages indicate problems fetching metadata, often due to permission or connectivity issues.- Errors returned from Bitrix24 API about missing or invalid IDs usually mean the specified entity or item does not exist.
- Authentication errors suggest misconfigured or expired credentials.
To resolve errors:
- Verify all input parameters are correct.
- Confirm credentials are properly set up and authorized.
- Check Bitrix24 API status and your network connection.