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, the Data Storage - Delete Item operation enables users to delete a specific item from a chosen entity type within Bitrix24. This is useful for automating cleanup tasks, removing outdated or incorrect records, or managing data lifecycle in Bitrix24 directly from n8n workflows.
Practical examples include:
- Automatically deleting a CRM lead after it has been converted or marked as invalid.
- Removing deals that have been closed and archived.
- Deleting custom Smart Process Automation (SPA) items when certain conditions are met.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: • OAuth2 (recommended for production) • Webhook (simpler but less secure) • API Key |
| Entity Type | The type of entity to work with, e.g., CRM_LEAD, CRM_DEAL, CRM_CONTACT. Specifies which Bitrix24 entity the item belongs to. |
| Item ID | The unique identifier of the item to delete within the specified entity type. |
| Options | Additional optional parameters: • Access Token: A token string for authentication override. • Filter: JSON object specifying filter criteria (not typically used for delete by ID). • Select: Comma-separated list of fields to select (not relevant for deletion). • Order: JSON object defining order criteria (not relevant for deletion). • Start: Number indicating start position for pagination (not relevant for deletion). |
Output
The node outputs an array of JSON objects representing the result of the delete operation. Typically, this will contain confirmation of deletion or any error messages if the operation failed.
- The
jsonoutput field contains the response from Bitrix24 API regarding the deletion status. - If the operation fails and "Continue On Fail" is enabled, the output includes an error object with keys such as
error(error message),resource(the resource name), andtimestamp. - The node does not output binary data.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods:
- OAuth2 authentication (recommended)
- Webhook URL
- API key authentication
- Requires proper configuration of credentials in n8n corresponding to the chosen authentication method.
- Uses Bitrix24 API endpoints internally to perform operations.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens leading to authorization errors.
- Incorrect
Entity TypeorItem IDcausing "item not found" errors. - Insufficient permissions on the Bitrix24 side to delete the specified item.
Error messages:
"error": "Item not found": Verify theEntity TypeandItem IDare correct and exist."error": "Unauthorized"or similar: Check that the authentication credentials are valid and have necessary scopes/permissions.- Network or API rate limit errors: Ensure stable internet connection and check Bitrix24 API usage limits.
Resolution tips:
- Double-check input parameters for typos or incorrect values.
- Refresh or reconfigure authentication credentials.
- Enable "Continue On Fail" in the node settings to handle errors gracefully in workflows.