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 Notify resource with the Send System Notification operation, this node sends system notifications to specified users within a Bitrix24 environment.
This is useful in scenarios where automated alerts or messages need to be sent to users based on workflow events, such as notifying a user about a new lead, task assignment, or system update. For example, a sales automation workflow could send a system notification to a salesperson when a high-priority deal is created.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: - OAuth2 (recommended for production) - Webhook (simpler but less secure) - API Key authentication |
| User ID | The numeric ID of the user who will receive the notification. Must be at least 1. |
| Message | The text content of the notification message to be sent. |
| Tag | A string tag used to categorize the notification. |
| Sub Tag | A more detailed sub-category tag for the notification. |
| Notification Type | The type of system notification to send: - Simple - Confirm - Buttons |
| Options | Additional options for the notification, including: - Attachments (JSON array) - URL Preview (boolean) - Sound (boolean) - Push (boolean) - Email (boolean) - Buttons (JSON array) - Confirm Text (string) - Decline Text (string) - Offset (number) - Filter (JSON object) - Order (JSON object) |
Output
The node outputs an array of items, each containing a json field with the response from Bitrix24 after sending the notification. If an error occurs and "Continue On Fail" is enabled, the output item will contain an error field describing the issue along with the resource name and timestamp.
If binary data were involved (not indicated here), it would typically represent files or attachments related to the notification, but this node primarily deals with JSON responses.
Dependencies
- Requires connection to a Bitrix24 instance.
- Supports three authentication methods: OAuth2, Webhook URL, or API Key.
- Proper credentials must be configured in n8n for the chosen authentication method.
- The node relies on Bitrix24's API endpoints to send notifications.
Troubleshooting
Common Issues:
- Invalid or missing user ID: Ensure the user ID exists in Bitrix24 and is correctly specified.
- Authentication failures: Verify that the OAuth2 token, webhook URL, or API key is valid and has sufficient permissions.
- Malformed JSON in options like attachments or buttons can cause API errors.
- Network connectivity issues between n8n and Bitrix24.
Error Messages:
- Errors returned by Bitrix24 API will be included in the output if "Continue On Fail" is enabled.
- Common errors include authentication errors, invalid parameters, or permission denied.
Resolution Tips:
- Double-check all input parameters for correctness.
- Validate JSON fields using external tools before inputting.
- Refresh or reconfigure credentials if authentication errors occur.
- Consult Bitrix24 API documentation for specific error codes.
Links and References
- Bitrix24 Official Website
- Bitrix24 REST API Documentation
- n8n Documentation (for general usage and credential setup)