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
This node integrates with the Bitrix24 platform, specifically providing functionality to retrieve notification schemas under the "Notify" resource with the "Get Schema" operation. It allows users to fetch notification settings and configurations such as attachments, URL previews, sounds, push notifications, emails, interactive buttons, and filtering options.
Common scenarios where this node is beneficial include:
- Automating retrieval of notification preferences or schemas from Bitrix24.
- Integrating Bitrix24 notifications into workflows for monitoring or alerting purposes.
- Customizing notification handling based on user-defined filters and options.
Practical example:
- A workflow that periodically fetches notification schemas to adjust how notifications are displayed or processed in an external system.
- Using the node to get notification settings before sending custom alerts or messages through Bitrix24.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key. |
| Options | Collection of optional parameters to customize the notification schema retrieval: |
| - Attachments | Attachments in JSON format to include with notifications. |
| - URL Preview | Boolean indicating whether to show URL preview in notifications. |
| - Sound | Boolean indicating whether to play a notification sound. |
| - Push | Boolean indicating whether to send push notifications. |
| Boolean indicating whether to send email notifications. | |
| - Buttons | Interactive buttons for the notification, provided in JSON format. |
| - Confirm Text | Text label for the confirm button in interactive notifications. |
| - Decline Text | Text label for the decline button in interactive notifications. |
| - Offset | Numeric offset for paginating or skipping notifications when retrieving them. |
| - Filter | JSON object specifying filter criteria to narrow down which notifications to retrieve. |
| - Order | JSON object specifying sort order for the retrieved notifications. |
Output
The node outputs an array of items, each containing a json field representing the response from Bitrix24's notification schema endpoint. The structure typically includes notification details according to the specified options and filters.
If errors occur and the node is configured to continue on failure, the output will contain an error object with fields:
error: Error message string.resource: The resource name ("notify").timestamp: ISO timestamp of the error occurrence.
The node does not explicitly handle binary data output.
Dependencies
- Requires authentication credentials for Bitrix24, which can be provided via OAuth2, webhook URL, or API key.
- Uses internal helper functions to make API calls to Bitrix24 endpoints.
- No additional external services beyond Bitrix24 API are required.
- Proper configuration of authentication credentials in n8n is necessary.
Troubleshooting
Common issues:
- Authentication failures due to incorrect or expired credentials.
- Malformed JSON in options like attachments, buttons, filter, or order causing API call failures.
- Network connectivity issues preventing access to Bitrix24 API.
- Incorrect usage of offset or filter parameters leading to empty or unexpected results.
Error messages:
- Errors thrown by the Bitrix24 API will be surfaced in the node output if "Continue On Fail" is enabled.
- Typical error messages may include authentication errors, invalid parameter formats, or API rate limits.
Resolutions:
- Verify and update authentication credentials.
- Ensure JSON inputs are valid and correctly formatted.
- Check network connectivity and Bitrix24 service status.
- Adjust filter and pagination parameters to valid values.
Links and References
- Bitrix24 Official API Documentation
- Bitrix24 Notifications API
- n8n documentation on creating custom nodes