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, the "Notify" resource with the "Send Personal Notification" operation enables sending customized notifications directly to a specified user within the Bitrix24 environment.
This node is beneficial in scenarios where automated alerts or messages need to be sent to individual users based on workflow events, such as notifying a sales representative about a new lead, alerting a manager about task updates, or sending reminders and confirmations.
Practical examples include:
- Sending a personalized message to a user when a deal stage changes.
- Alerting a user about an upcoming meeting or deadline.
- Delivering interactive notifications with buttons for quick responses.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: OAuth2 (recommended), Webhook (simpler but less secure), or API Key. |
| User ID | Numeric ID of the user to whom the notification will be sent. |
| Message | Text content of the notification message. |
| Tag | A string tag used to categorize the notification. |
| Sub Tag | A more detailed sub-category tag for the notification. |
| Options | Collection of additional options including: |
| - Attachments | JSON array specifying attachments to include with the notification. |
| - URL Preview | Boolean indicating whether to show URL previews in the notification. |
| - Sound | Boolean indicating whether to play a sound when the notification arrives. |
| - Push | Boolean indicating whether to send a push notification. |
| Boolean indicating whether to send the notification via email. | |
| - Buttons | JSON array defining interactive buttons for the notification. |
| - Confirm Text | Text label for a confirm button in the notification. |
| - Decline Text | Text label for a decline button in the notification. |
| - Offset | Numeric offset for retrieving notifications (used internally). |
| - Filter | JSON object defining filter criteria for notifications (used internally). |
| - Order | JSON object defining sort order for notifications (used internally). |
Output
The node outputs an array of items, each containing a json field representing the response from the Bitrix24 API after attempting to send the notification. The structure typically includes confirmation details or error information if the request failed.
If the node encounters an error during execution and the "Continue On Fail" option is enabled, it outputs an item with an error property describing the issue, along with the resource name and a timestamp.
The node does not output binary data.
Dependencies
- Requires valid authentication credentials for Bitrix24, which can be provided via OAuth2, webhook URL, or API key.
- The node depends on Bitrix24's API endpoints to send notifications.
- Proper configuration of authentication credentials in n8n is necessary.
- Network access to Bitrix24 services must be available.
Troubleshooting
Common Issues:
- Invalid or expired authentication credentials may cause authorization errors.
- Incorrect user ID may result in failure to deliver the notification.
- Malformed JSON in attachments or buttons options can cause API request failures.
- Network connectivity issues can prevent communication with Bitrix24 API.
Error Messages:
- Errors returned by the Bitrix24 API are passed through in the output under the
errorfield if "Continue On Fail" is enabled. - Common error messages include authentication failures, invalid parameters, or permission denials.
- Errors returned by the Bitrix24 API are passed through in the output under the
Resolutions:
- Verify that the selected authentication method is correctly configured and active.
- Ensure the user ID corresponds to a valid Bitrix24 user.
- Validate JSON syntax in complex fields like attachments and buttons.
- Check network connectivity and firewall settings.