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 interacts with Bitrix24, a CRM and business platform, to perform various operations on its resources. Specifically, the "Lists" resource with the "Delete Section" operation allows users to delete a section within a specified list in Bitrix24. This is useful for managing hierarchical data structures or categories within lists, such as removing outdated or irrelevant sections.
Practical examples:
- Automatically cleaning up project task lists by deleting completed or obsolete sections.
- Managing product catalogs by removing discontinued category sections.
- Organizing contact groups by deleting unused segments.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key. |
| List ID | The unique identifier of the list containing the section to delete. |
| Section ID | The unique identifier of the section to be deleted from the list. |
| Options | Additional optional parameters: - Access Token: Use a specific access token instead of credentials. - Filter: JSON object to filter results. - Order: JSON object specifying sort order. - Select: Comma-separated list of fields to select. |
Output
The node outputs a JSON object representing the result of the delete operation. Typically, this will confirm whether the section was successfully deleted or provide error details if the operation failed.
If the node supports binary data output, it is not indicated here; thus, the output is primarily JSON-based.
Example output structure:
{
"result": {
"success": true,
"deletedSectionId": "123"
}
}
or in case of failure:
{
"error": "Section not found",
"resource": "lists",
"timestamp": "2024-06-01T12:00:00Z"
}
Dependencies
- Requires an active connection to Bitrix24 via one of the supported authentication methods (OAuth2, webhook URL, or API key).
- Needs proper configuration of credentials in n8n corresponding to the chosen authentication method.
- May require appropriate permissions in Bitrix24 to delete sections within lists.
Troubleshooting
Common issues:
- Invalid or missing List ID or Section ID leading to errors like "Section not found".
- Insufficient permissions causing authorization errors.
- Incorrect authentication setup resulting in failed API calls.
Error messages and resolutions:
"Section not found": Verify that the provided Section ID exists within the specified List ID."Unauthorized"or"Access denied": Check that the authentication credentials are valid and have sufficient rights."Invalid token": If using an access token override, ensure the token is current and has not expired.- Network or connectivity errors: Confirm that Bitrix24 service is reachable and no firewall blocks exist.