Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

This node integrates with the Bitrix24 platform, specifically enabling operations on notifications within Bitrix24. The "Delete Notification" operation under the "Notify" resource allows users to delete a specific notification by its ID. This is useful in scenarios where automated workflows need to manage or clean up notifications programmatically, such as removing outdated alerts, clearing notifications after processing, or managing user notification states.

Practical examples include:

  • Automatically deleting a notification once a related task is completed.
  • Cleaning up notifications that are no longer relevant to reduce clutter.
  • Integrating with other systems to synchronize notification status by deleting them from Bitrix24.

Properties

Name Meaning
Authentication Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook (simpler), or API Key.
Notification ID The unique identifier of the notification to be deleted.
Options Additional optional parameters for notification handling:
- Attachments JSON array specifying attachments related to the notification.
- URL Preview Boolean indicating whether to show URL preview in the notification.
- Sound Boolean indicating whether to play a sound when the notification is sent.
- Push Boolean indicating whether to send a push notification.
- Email Boolean indicating whether to send an email notification.
- 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 paginating notifications retrieval (not directly relevant for deletion).
- Filter JSON object defining filter criteria for notifications (not directly relevant for deletion).
- Order JSON object defining sort order for notifications (not directly relevant for deletion).

Output

The node outputs an array of items corresponding to the processed notifications. Each item contains a json field with the response data from Bitrix24 regarding the deletion operation.

If an error occurs and the node is configured to continue on failure, 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 authentication credentials for Bitrix24 via one of the supported methods: OAuth2, webhook URL, or API key.
  • Relies on Bitrix24's API endpoints to perform notification management.
  • No additional external dependencies beyond standard HTTP requests to Bitrix24.

Troubleshooting

  • Common Issues:

    • Invalid or missing Notification ID will cause the operation to fail.
    • Incorrect or expired authentication credentials will result in authorization errors.
    • Network connectivity issues may prevent communication with Bitrix24 API.

  • Error Messages:

    • Errors returned from Bitrix24 API will be propagated; typical messages include "Notification not found" or "Access denied".
    • If the node is set to continue on failure, errors will appear in the output JSON under the error property.

  • Resolutions:

    • Verify the Notification ID is correct and exists in Bitrix24.
    • Ensure authentication credentials are valid and have necessary permissions.
    • Check network connectivity and API endpoint accessibility.

Links and References

Discussion