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 to send public notifications to a specified chat. It supports multiple authentication methods including OAuth2, webhook URLs, and API keys, allowing flexible and secure access depending on user preference or environment.
Typical use cases include:
- Broadcasting announcements or alerts to team chats within Bitrix24.
- Sending automated messages triggered by workflows or external events.
- Enhancing communication by attaching interactive buttons, sounds, or email notifications.
For example, a sales automation workflow could notify a sales team chat about a new lead or deal update using this node.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook URL (simpler), or API Key |
| Chat ID | Numeric identifier of the chat where the notification will be sent (minimum value 1) |
| Message | Text content of the notification message |
| Tag | Optional tag for categorizing the notification |
| Sub Tag | Optional sub-tag for more detailed categorization |
| Options | Collection of additional settings: |
| - Attachments | JSON array of attachments to include in the notification |
| - URL Preview | Boolean to enable or disable URL preview in the message |
| - Sound | Boolean to enable or disable playing a notification sound |
| - Push | Boolean to enable or disable sending a push notification |
| Boolean to enable or disable sending an email notification | |
| - Buttons | JSON array defining interactive buttons for the notification |
| - Confirm Text | Text label for a confirm button |
| - Decline Text | Text label for a decline button |
| - Offset | Numeric offset used when retrieving notifications (not typically used for sending) |
| - Filter | JSON object specifying filter criteria (not typically used for sending) |
| - Order | JSON object specifying sort order (not typically used for sending) |
Output
The node outputs an array of items, each containing a json property with the response from Bitrix24 after sending the notification. The structure typically includes confirmation details or error information if the operation failed.
If an error occurs and "Continue On Fail" is enabled, the output item will contain an error field with the error message, along with the resource name and a timestamp.
No binary data output is produced by this node.
Dependencies
- Requires valid authentication credentials for Bitrix24 via one of the supported methods (OAuth2 token, webhook URL, or API key).
- Network access to Bitrix24 API endpoints.
- Proper configuration of authentication credentials in n8n is necessary before using this node.
Troubleshooting
Common Issues:
- Invalid or expired authentication credentials causing authorization failures.
- Incorrect Chat ID leading to failure in sending notifications.
- Malformed JSON in attachments or buttons options causing request errors.
Error Messages:
- Authorization errors: Check that the selected authentication method is correctly configured and tokens/keys are valid.
- Validation errors: Ensure required fields like Chat ID and Message are provided and properly formatted.
- JSON parsing errors: Verify that JSON inputs for attachments and buttons are well-formed.
Resolution Tips:
- Re-authenticate or refresh credentials if authorization fails.
- Double-check numeric Chat ID values and ensure the chat exists.
- Use JSON validators to confirm correctness of JSON-formatted options.