Actions89
- Direct API Actions
- CRM Actions
- Task Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Chat Actions
Overview
The Bitrix24 node allows interaction with the Bitrix24 CRM and business platform. Specifically, for the Data Storage resource with the Delete operation, this node deletes a specified entity from Bitrix24 based on its type and ID.
This operation is useful in scenarios where you need to programmatically remove CRM records such as leads, deals, contacts, or custom entities from your Bitrix24 account. For example, automating cleanup of outdated leads or removing test data after import processes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
| Entity Type | The type of entity to delete, e.g., CRM_LEAD, CRM_DEAL, CRM_CONTACT. |
| Entity ID | The unique identifier of the entity to delete. |
| Options | Additional optional parameters: - Access Token: token string for authentication - Filter: JSON object to filter entities (not typically used for delete by ID) - Select: Comma-separated fields to select - Order: JSON object defining order criteria - Start: Number indicating start position for pagination |
Note: The "Options" collection is more relevant for other operations like listing or filtering entities but is available here as well.
Output
The output of the delete operation is an array containing one item per input item processed. Each item’s json field will contain the response from Bitrix24 API regarding the deletion result. Typically, this includes confirmation of successful deletion or error details if the operation failed.
If the node encounters an error and is configured to continue on failure, it outputs an object with an error property describing the issue, along with the resource name and a timestamp.
No binary data output is involved in this operation.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2, webhook URL, or API key).
- The node internally uses Bitrix24 API endpoints to perform actions.
- No additional external dependencies beyond standard n8n credential setup are required.
Troubleshooting
Common Issues:
- Invalid or expired authentication tokens can cause authorization failures.
- Incorrect or non-existent Entity ID will result in errors indicating the entity was not found.
- Insufficient permissions in Bitrix24 user roles may prevent deletion.
Error Messages:
"error": "Entity not found"— Verify the Entity ID and Entity Type are correct."error": "Access denied"— Check that the authentication method has sufficient rights.- Network or API errors — Ensure connectivity and that Bitrix24 API limits are not exceeded.
Resolution Tips:
- Refresh or reconfigure authentication credentials.
- Double-check entity identifiers and types.
- Review Bitrix24 user permissions and API access scopes.