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 integrates with the Bitrix24 CRM and business platform, enabling automation workflows to interact with various Bitrix24 resources. Specifically, the Notify - Answer Notification operation allows users to send a response to an existing notification within Bitrix24. This is useful in scenarios where automated systems or users need to programmatically reply to notifications, such as confirming tasks, responding to alerts, or interacting with system messages.
Practical examples include:
- Automatically acknowledging a system notification after processing.
- Sending a custom message reply to a personal or public notification.
- Responding to interactive notifications with buttons or attachments.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24. Options: β’ OAuth2 (recommended for production) β’ Webhook (simpler but less secure) β’ API Key authentication |
| Message | The text content of the notification reply message. Required. |
| Notification ID | The unique identifier of the notification to which the answer is sent. Required. |
| Options | Additional optional settings for the notification reply: β’ Attachments: JSON array of files or media to attach β’ URL Preview: Show preview for URLs (true/false) β’ Sound: Play notification sound (true/false) β’ Push: Send push notification (true/false) β’ Email: Send email notification (true/false) β’ Buttons: JSON array defining interactive buttons β’ Confirm Text: Text label for confirm button β’ Decline Text: Text label for decline button β’ Offset: Numeric offset for pagination (not typically used here) β’ Filter: JSON object to filter notifications (not typically used here) β’ Order: JSON object to specify sort order (not typically used here) |
Output
The node outputs an array of items, each containing a json object representing the result of the notification answer operation. The exact structure depends on the Bitrix24 API response but generally includes confirmation of the action or details about the answered notification.
If an error occurs 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.
The node does not output binary data.
Dependencies
- Requires connection to a Bitrix24 instance.
- Supports three authentication methods: OAuth2, Webhook URL, or API Key credential.
- Proper configuration of credentials in n8n is necessary depending on the chosen authentication method.
- Network access to Bitrix24 API endpoints is required.
Troubleshooting
Common issues:
- Invalid or expired authentication credentials can cause authorization failures.
- Incorrect Notification ID may lead to errors indicating the notification was not found.
- Malformed JSON in options like attachments or buttons can cause request failures.
- Insufficient permissions in Bitrix24 user account to answer notifications.
Error messages:
- Errors returned from Bitrix24 API are surfaced in the node output if "Continue On Fail" is enabled.
- Typical errors include authentication errors, invalid parameters, or API rate limits.
Resolutions:
- Verify and refresh authentication credentials.
- Double-check the Notification ID value.
- Validate JSON syntax for complex option fields.
- Ensure the Bitrix24 user has appropriate rights to manage notifications.