Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

This node interacts with Bitrix24's Lists resource to delete a specific element from a list. It is useful in scenarios where you need to programmatically remove entries from custom lists managed within Bitrix24, such as cleaning up outdated records, removing test data, or automating data lifecycle management.

For example, if you have a list of project tasks in Bitrix24 and want to automatically delete completed or canceled tasks based on certain criteria, this node can be configured to delete those elements by their IDs.

Properties

Name Meaning
Authentication Method to authenticate with Bitrix24: OAuth2 (recommended), Webhook URL (simpler but less secure), or API Key authentication.
List ID The unique identifier of the list from which an element will be deleted.
Element ID The unique identifier of the element within the list that should be deleted.
Options Additional optional parameters:
• Access Token: Override the default token with a specific one.
• Filter: JSON object to filter elements (not typically used for deletion by ID).
• Order: JSON object specifying sort order.
• Select: Comma-separated fields to select (not typically relevant for deletion).

Output

The output contains a JSON object representing the result of the delete operation. Typically, this will confirm whether the element was successfully deleted or provide error information if the deletion failed.

If the operation fails and "Continue On Fail" is enabled, the output JSON will include an error field with the error message, the resource name ("lists"), and a timestamp.

No binary data output is produced by 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 API endpoints for list and element management.
  • No additional external services are required beyond Bitrix24 itself.
  • Proper configuration of credentials in n8n is necessary to authorize API calls.

Troubleshooting

  • Common Issues:

    • Invalid or expired authentication tokens may cause authorization failures.
    • Incorrect List ID or Element ID will result in errors indicating the element or list was not found.
    • Insufficient permissions in Bitrix24 for deleting list elements can cause access denied errors.

  • Error Messages:

    • "Element not found": Verify that the Element ID exists in the specified List ID.
    • "Access denied" or "Unauthorized": Check that the authentication credentials are correct and have sufficient permissions.
    • Network or API errors: Ensure Bitrix24 service is reachable and your network allows outbound requests.

  • Resolutions:

    • Refresh or reconfigure authentication credentials.
    • Double-check the List ID and Element ID values.
    • Confirm user permissions in Bitrix24 for list element deletion.
    • Enable "Continue On Fail" in the node settings to handle errors gracefully during workflows.

Links and References

Discussion