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
This node integrates with the Bitrix24 CRM and business platform, allowing users to perform various operations on CRM entities. Specifically, for the CRM - Delete operation, it enables deleting a record of a specified entity type (such as Contact, Deal, Lead, Company, etc.) by its unique ID.
Common scenarios where this node is beneficial include:
- Automating cleanup of outdated or invalid CRM records.
- Integrating Bitrix24 with other systems to synchronize deletions.
- Managing CRM data lifecycle programmatically within workflows.
For example, you might use this node to delete a contact after unsubscribing them from your mailing list or remove a deal that was lost or canceled.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
| Entity | The type of CRM entity to operate on. Options include: - Contact - Deal - Lead - Company - Quote - Invoice - Product - Activity |
| Record ID | The unique identifier of the record to delete. This is required to specify which record will be removed. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this includes confirmation of deletion or any error messages returned by the Bitrix24 API.
If an error occurs and "Continue On Fail" is enabled, the output JSON will contain an error field with the error message, along with metadata such as the resource name and timestamp.
No binary data output is involved in this operation.
Dependencies
- Requires authentication credentials for Bitrix24 via one of the supported methods (OAuth2, Webhook URL, or API Key).
- Relies on Bitrix24's REST API endpoints to perform CRM operations.
- No additional external services are needed beyond Bitrix24 itself.
- Proper configuration of credentials in n8n is necessary for successful API calls.
Troubleshooting
Common Issues:
- Invalid or missing Record ID: The node requires a valid record ID to delete; ensure this is correctly provided.
- Insufficient permissions: The authenticated user or API key must have rights to delete the specified entity.
- Network or API errors: Connectivity issues or Bitrix24 service outages can cause failures.
Error Messages:
- Errors returned from Bitrix24 API will be surfaced in the node output if "Continue On Fail" is enabled.
- Typical errors include "Record not found," "Access denied," or "Invalid authentication."
Resolution Tips:
- Verify the Record ID exists and is correct.
- Check that the authentication credentials are valid and have appropriate scopes/permissions.
- Review Bitrix24 API limits and status.
- Enable "Continue On Fail" to capture error details for debugging.