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 interaction with the Bitrix24 CRM and business platform. Specifically, the "Notify" resource with the "Get Notifications" operation enables users to retrieve notifications from their Bitrix24 account. This is useful for automating workflows that depend on notification data, such as alerting teams about new messages, tasks, or system events within Bitrix24.
Practical examples include:
- Fetching recent notifications to trigger follow-up actions in other systems.
- Monitoring notification streams to update dashboards or send alerts.
- Filtering notifications based on criteria like type or date to process only relevant information.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook URL (simpler but less secure), or API Key authentication. |
| Options | Collection of optional parameters to customize the notification retrieval: |
| - Attachments | Attachments included with the notification, provided in JSON format. |
| - URL Preview | Boolean flag to enable or disable showing URL previews in notifications. |
| - Sound | Boolean flag to enable or disable playing a sound when notification arrives. |
| - Push | Boolean flag to enable or disable sending push notifications. |
| Boolean flag to enable or disable sending email notifications. | |
| - Buttons | Interactive buttons for the notification, specified in JSON format. |
| - Confirm Text | Text label for a confirm button in the notification UI. |
| - Decline Text | Text label for a decline button in the notification UI. |
| - Offset | Numeric offset to paginate through notifications. |
| - Filter | JSON object specifying filter criteria to narrow down which notifications are retrieved. |
| - Order | JSON object specifying sorting order for the notifications returned. |
Output
The node outputs an array of items where each item contains a json field representing a notification object retrieved from Bitrix24. The structure of each notification depends on the Bitrix24 API response and may include fields such as notification text, sender, timestamp, attachments, and interactive elements.
If binary data is present (e.g., attachments), it would be included accordingly, but this node primarily deals with JSON notification data.
Dependencies
- Requires connection to Bitrix24 via one of the supported authentication methods: OAuth2, webhook URL, or API key.
- Needs proper configuration of credentials in n8n corresponding to the chosen authentication method.
- Relies on Bitrix24 API endpoints to fetch notifications.
Troubleshooting
- Authentication errors: Ensure that the selected authentication method is correctly configured with valid credentials or tokens.
- API call failures: Network issues or incorrect permissions in Bitrix24 can cause errors; verify API access rights.
- Invalid JSON in options: The
attachments,buttons,filter, andorderproperties expect valid JSON strings; malformed JSON will cause errors. - Empty results: If no notifications are returned, check the filter criteria and offset values to ensure they match existing notifications.
- Continue on Fail: If enabled, the node returns error details in the output instead of failing the workflow.