Bitrix24Install

Overview

The Bitrix24 node allows interaction with the Bitrix24 CRM and business platform. Specifically, for the Events resource and the Unregister Handler operation, this node enables users to unregister or unbind event handlers that were previously registered to listen for specific Bitrix24 events.

This functionality is useful in scenarios where you want to stop receiving notifications or webhook callbacks for certain events, such as when a CRM lead is added or updated, a deal is created or modified, tasks are added or updated, or new users are added. For example, if you had set up an automation to trigger on "CRM Lead Add" events but no longer need it, you can use this operation to unregister the handler cleanly.

Properties

Output

The node outputs JSON data representing the result of the unregister operation. If successful, the output typically confirms that the event handler was unregistered. In case of failure, the output may contain an error message describing what went wrong.

The output structure includes:

• json: An object containing either the success response or an error object.
• If an error occurs and the node is configured to continue on failure, the output JSON will include:
  • error: The error message string.
  • resource: The resource name ("events").
  • timestamp: The ISO timestamp when the error occurred.

No binary data output is involved in 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 to manage event handlers.
• Proper configuration of credentials within n8n is necessary to authenticate API calls.

Troubleshooting

• Common Issues:

  • Incorrect or expired authentication credentials leading to authorization errors.
  • Attempting to unregister an event handler that does not exist or was never registered.
  • Network connectivity issues preventing communication with Bitrix24 API.

• Error Messages:

  • Errors returned from Bitrix24 API will be surfaced in the node output under the error field.
  • If the node throws an exception, ensure that the authentication method matches the credential provided.
  • To resolve errors, verify credentials, check event type correctness, and confirm the handler exists before attempting to unregister.

Links and References

• Bitrix24 Official API Documentation
• Bitrix24 Events and Webhooks Guide
• n8n Documentation on Credentials