Bitrix24Install

Overview

This node integrates with the Bitrix24 CRM and business platform, allowing users to perform various operations on CRM entities. Specifically, for the CRM - Delete operation, it enables deleting a record of a specified entity type (such as Contact, Deal, Lead, etc.) by its unique ID.

Common scenarios where this node is beneficial include:

• Automating cleanup of outdated or invalid CRM records.
• Integrating with other systems to remove CRM entries when corresponding data is deleted elsewhere.
• Managing CRM data lifecycle programmatically within workflows.

For example, you might use this node to delete a contact after unsubscribing them from your mailing list or to remove a deal that was canceled.

Properties

Output

The node outputs an array of items, each containing a json object representing the result of the delete operation. On success, the output typically confirms the deletion or returns relevant metadata from Bitrix24.

If the operation fails and "Continue On Fail" is enabled, the output will contain an error object with:

• error: The error message describing what went wrong.
• resource: The resource name ("crm").
• timestamp: The ISO timestamp when the error occurred.

The node does not output binary data.

Dependencies

• Requires connection to a Bitrix24 instance.
• Needs one of the following authentication methods configured in n8n:
  • OAuth2 credentials for Bitrix24.
  • Bitrix24 webhook URL.
  • Bitrix24 API key.
• The node uses Bitrix24's REST API endpoints internally to perform operations.

Troubleshooting

Common Issues

• Invalid Record ID: If the provided Record ID does not exist or is incorrect, the delete operation will fail.
• Insufficient Permissions: The authenticated user or API key may lack permissions to delete certain CRM entities.
• Authentication Errors: Misconfigured OAuth2 tokens, expired tokens, or invalid webhook URLs/API keys can cause authentication failures.
• Network or API Errors: Temporary network issues or Bitrix24 API downtime can interrupt the operation.

Error Messages and Resolutions

• "Record not found": Verify the Record ID is correct and exists in the specified entity.
• "Access denied" or "Permission denied": Check that the credentials used have sufficient rights to delete records.
• "Authentication failed": Re-authenticate or verify the correctness of the OAuth2 token, webhook URL, or API key.
• Other API errors: Review the error message details; consult Bitrix24 API documentation or support if needed.

Enabling "Continue On Fail" allows workflows to handle errors gracefully without stopping execution.

Links and References

• Bitrix24 REST API Documentation
• Bitrix24 CRM Entities Overview
• n8n Documentation - Bitrix24 Node