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 the Bitrix24 platform, specifically allowing operations on various resources such as CRM entities and business lists. The "Lists" resource with the "Delete" operation enables users to delete a specified list from their Bitrix24 account.
Common scenarios for this node include automating the cleanup of outdated or unnecessary lists in Bitrix24, managing data lifecycle by removing obsolete entries, or integrating Bitrix24 list management into broader workflows that require dynamic list deletion.
For example, a user might set up an automation that deletes a project task list once the project is completed, or remove temporary contact lists created during marketing campaigns.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook (simpler but less secure), or API Key authentication. |
| List ID | The unique identifier of the list to be deleted. |
| Options | Additional optional parameters: |
| - Access Token | Use a specific access token instead of the one from credentials. |
| - Filter | JSON-formatted filter criteria (not typically used for delete but available). |
| - Order | JSON-formatted sort order (not typically used for delete but available). |
| - Select | Comma-separated list of fields to select (not typically used for delete but available). |
Output
The node outputs a JSON object representing the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide error details if it failed.
If the operation fails and the node is configured to continue on failure, the output JSON will contain an error field with the error message, the resource name, and a timestamp.
No binary data output is involved in this operation.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods: OAuth2, webhook URL, or API key.
- Needs appropriate permissions in Bitrix24 to delete lists.
- No additional external dependencies beyond Bitrix24 API access.
Troubleshooting
Common Issues:
- Invalid or missing List ID: Ensure the List ID provided exists and is correct.
- Insufficient permissions: The authenticated user must have rights to delete lists.
- Authentication errors: Verify that the chosen authentication method is correctly configured and valid.
- Network or API errors: Temporary connectivity issues or Bitrix24 API downtime can cause failures.
Error Messages:
- Errors returned from Bitrix24 API will be included in the output JSON under the
errorfield if "continue on fail" is enabled. - Common messages may indicate invalid credentials, missing list, or permission denied.
- Errors returned from Bitrix24 API will be included in the output JSON under the
Resolution:
- Double-check List ID and ensure it exists.
- Confirm authentication credentials are valid and have necessary scopes.
- Retry after some time if network/API issues occur.