Bitrix icon

Bitrix

Consume Bitrix24 REST API

Actions31

Overview

This node integrates with the Bitrix24 REST API to perform operations on CRM items. Specifically, the "Delete" operation under the "Item" resource allows users to delete a CRM record of a specified entity type by its ID. This is useful for automating cleanup tasks, removing outdated or incorrect records, or managing data lifecycle within Bitrix24.

Practical examples include:

  • Automatically deleting a CRM item when it no longer meets certain criteria.
  • Removing test or temporary records after processing.
  • Integrating with other workflows that require deletion of CRM entries based on external triggers.

Properties

Name Meaning
Authentication Method of authentication to use: either OAuth2 or Webhook.
Entity Type Name or ID Identifier of the system or user-defined CRM entity type to operate on (e.g., Deal, Contact).
ID The unique identifier of the CRM record to delete.

Note: The property "Use Original UF Names" exists but is hidden and not applicable for the Delete operation.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide error details if it failed. There is no binary output associated with this operation.

Dependencies

  • Requires an active connection to Bitrix24 via either OAuth2 or Webhook authentication.
  • Proper credentials must be configured in n8n for the chosen authentication method.
  • The node depends on Bitrix24's REST API availability and permissions granted to the authenticated user.

Troubleshooting

  • Common issues:

    • Invalid or missing record ID: Ensure the ID provided corresponds to an existing CRM item.
    • Insufficient permissions: The authenticated user must have rights to delete the specified entity.
    • Incorrect entity type: The entityTypeId must match a valid CRM entity type in Bitrix24.
    • Network or API errors: Check connectivity and Bitrix24 service status.

  • Error messages:

    • "Record not found": The ID does not exist or is incorrect.
    • "Access denied": Permissions issue; verify authentication and user roles.
    • "Invalid entity type": The entityTypeId is invalid or unsupported.

Resolving these typically involves verifying input parameters, checking credential validity, and ensuring the Bitrix24 account has appropriate access.

Links and References

Discussion