Bitrix24Install

Overview

The Bitrix24 node allows users to interact with the Bitrix24 CRM and business platform. Specifically, for the Events resource with the Register Handler operation, this node enables registering event handlers (webhooks) that listen for specific Bitrix24 events such as CRM lead additions or updates, deal changes, task creations, and user additions.

This functionality is beneficial in scenarios where you want to automate workflows triggered by changes or actions within Bitrix24. For example, when a new lead is added in Bitrix24, you can automatically trigger downstream processes like sending notifications, updating external systems, or logging data.

Practical examples:

• Automatically notify your sales team via Slack when a new CRM lead is added.
• Sync updated deal information from Bitrix24 to an external ERP system.
• Trigger custom business logic whenever a new task is created in Bitrix24.

Properties

Output

The node outputs JSON data representing the result of the event handler registration process. This typically includes confirmation details about the registered webhook or any error messages if the registration failed.

If the node encounters an error during execution and "Continue On Fail" is enabled, it outputs a JSON object containing:

• error: The error message
• resource: The resource name ("events")
• timestamp: The ISO timestamp of the error occurrence

The node does not output binary data.

Dependencies

• Requires valid authentication credentials for Bitrix24 using one of the supported methods: OAuth2, Webhook URL, or API Key.
• The node depends on Bitrix24's API endpoints to register event handlers.
• Proper configuration of the handler URL is necessary to receive event callbacks from Bitrix24.
• Network accessibility of the handler URL from Bitrix24 servers is required.

Troubleshooting

• Common Issues:

  • Incorrect or expired authentication credentials may cause authorization failures.
  • Invalid or unreachable handler URL will prevent event delivery.
  • Selecting unsupported or misspelled event types will cause registration errors.

• Error Messages:

  • Errors returned from Bitrix24 API calls will be surfaced in the node output under the error field.
  • If the node throws an exception, enabling "Continue On Fail" will allow workflow continuation and provide error details in the output.

• Resolutions:

  • Verify and refresh authentication credentials.
  • Ensure the handler URL is publicly accessible and correctly configured to accept POST requests.
  • Double-check the event type selection matches Bitrix24's supported event names.

Links and References

• Bitrix24 Official API Documentation
• Bitrix24 Webhooks Guide
• Bitrix24 Events and Automation