Actions290
- Task Actions
- Direct API Actions
- CRM Actions
- User Actions
- SPA Actions
- Activity Actions
- Automation Actions
- Document Generator Actions
- Data Storage Actions
- Get Entity
- Add Entity
- Update Entity
- Delete Entity
- Get Entity Rights
- Get Entity Sections
- Add Entity Section
- Update Entity Section
- Delete Entity Section
- Get Entity Item
- Add Entity Item
- Update Entity Item
- Delete Entity Item
- Get Entity Item Properties
- Add Entity Item Property
- Update Entity Item Property
- Delete Entity Item Property
- Chat Actions
- User Field Actions
- File Actions
- User Field Config Actions
- Duplicate Actions
- Timeline Actions
- Disk Actions
- Upload File
- Download File
- Delete File
- Get File Info
- List Files
- Create Folder
- Delete Folder
- Get Storage Info
- Get Storages
- Get Storage
- Get Folders
- Get Folder
- Add Folder
- Update Folder
- Copy Folder
- Move Folder
- Rename Folder
- Get Files
- Get File
- Copy File
- Move File
- Rename File
- Share Item
- Get Shared Items
- Get Sharing Rights
- Update Sharing Rights
- Workflow Actions
- Status Actions
- Calendar Actions
- Chatbot Actions
- Events Actions
- Lists Actions
- Product Actions
- Open Lines Actions
- Telephony Actions
- Register External Call
- Finish External Call
- Hide External Call
- Show External Call
- Search CRM Entities
- Attach Call Record
- Get External Line
- Add External Line
- Update External Line
- Delete External Line
- Get Voximplant Statistics
- Get Voximplant Line
- Get Voximplant SIP Connector
- Get Voximplant SIP Line
- Add Voximplant SIP Line
- Update Voximplant SIP Line
- Delete Voximplant SIP Line
- Message Service Actions
- Notify Actions
Overview
The Bitrix24 node allows users to interact with the Bitrix24 CRM and business platform. Specifically, for the Events resource and the Get Handlers operation, this node retrieves event handler information from Bitrix24. This can be useful in automation workflows where you want to monitor or react to specific events occurring within the Bitrix24 environment, such as changes in CRM data or system notifications.
Practical examples include:
- Automatically triggering follow-up actions when a new lead is created.
- Monitoring deal stage changes to update external systems.
- Fetching webhook handlers to integrate Bitrix24 events with other applications.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key |
Output
The node outputs an array of items, each containing a json object with the data returned by Bitrix24 related to event handlers. The exact structure depends on the Bitrix24 API response for event handlers but typically includes details about available event handlers, their types, and configurations.
If an error occurs during execution and "Continue On Fail" is enabled, the output will contain an item with an error field describing the issue, along with the resource name and a timestamp.
No binary data output is indicated in the source code.
Dependencies
- Requires authentication credentials configured in n8n for Bitrix24 using one of the supported methods (OAuth2, Webhook URL, or API Key).
- Relies on Bitrix24's API endpoints to fetch event handler data.
- Uses internal helper functions to make standardized API calls to Bitrix24.
Troubleshooting
Common issues:
- Authentication failures due to incorrect or expired credentials.
- API rate limits or connectivity problems with Bitrix24.
- Missing or incorrect resource/operation parameters.
Error messages:
- Errors thrown by the Bitrix24 API are caught and can be output if "Continue On Fail" is enabled.
- Typical error message format includes the error description, resource name, and timestamp.
Resolution tips:
- Verify that the selected authentication method is correctly configured.
- Ensure network connectivity to Bitrix24 services.
- Check that the resource and operation parameters are valid and supported.