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 node integrates with the Bitrix24 platform, specifically allowing interaction with its CRM and business resources. For the Data Storage resource with the Delete Section operation, it enables users to delete a specific section within an entity type in Bitrix24. This is useful for managing organizational structures or categories within CRM entities such as leads, deals, contacts, etc.
Practical scenarios include:
- Removing obsolete or incorrect sections from CRM entities.
- Automating cleanup of data structures during synchronization or migration processes.
- Managing hierarchical data by programmatically deleting sections no longer needed.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key. |
| Entity Type | The type of CRM entity to work with, e.g., CRM_LEAD, CRM_DEAL, CRM_CONTACT. |
| Section ID | The unique identifier of the section to be deleted. |
| Options | Additional optional parameters including: |
| - Access Token | A token string for authentication purposes. |
| - Filter | JSON object specifying filter criteria (not typically used for deletion but available). |
| - Select | Comma-separated list of fields to select (not typically used for deletion but available). |
| - Order | JSON object defining order criteria (not typically used for deletion but available). |
| - Start | Number indicating start position for pagination (not typically used for deletion but available). |
Output
The output of this operation is a JSON object representing the result of the delete action. Typically, it will confirm whether the section was successfully deleted or provide error details if the operation failed.
If the node encounters an error and "Continue On Fail" is enabled, the output JSON will contain an error field with the error message, along with metadata about the resource and timestamp.
No binary data output is expected for 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 REST API endpoints to perform operations.
- Proper configuration of authentication credentials in n8n is necessary.
- Network access to Bitrix24 API endpoints must be available.
Troubleshooting
Common Issues:
- Invalid or expired authentication tokens leading to authorization errors.
- Incorrect or non-existent Section ID causing "not found" errors.
- Insufficient permissions for the authenticated user to delete sections.
- Network connectivity issues preventing API calls.
Error Messages:
"error": "Invalid authentication": Check and refresh your authentication credentials."error": "Section not found": Verify the Section ID is correct and exists."error": "Access denied": Ensure the authenticated user has permission to delete sections.- Timeout or network errors: Confirm network connectivity and Bitrix24 API availability.
Resolution Tips:
- Re-authenticate or update credentials if authentication fails.
- Double-check input parameters, especially Section ID and Entity Type.
- Review Bitrix24 user permissions and roles.
- Enable "Continue On Fail" to handle errors gracefully in workflows.