Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

This node integrates with the Bitrix24 platform, specifically providing functionality to manage notifications. The "Notify" resource with the "Mark as Unread" operation allows users to mark a specific notification as unread in their Bitrix24 account.

Common scenarios for this node include:

  • Automating notification management workflows where certain notifications need to be flagged as unread for follow-up.
  • Integrating Bitrix24 notifications into broader business processes, ensuring important alerts are not missed by resetting their read status.
  • Use cases in customer support or sales teams where notifications about leads, deals, or tasks require re-attention.

Example: After processing a notification automatically, you might want to mark it as unread so that a team member can review it manually later.

Properties

Name Meaning
Authentication Method of authenticating with Bitrix24: OAuth2 (recommended), Webhook URL (simpler), or API Key
Notification ID The unique identifier of the notification to mark as unread (string, required)
Options Additional optional settings for the notification, including:
- Attachments JSON array of attachments to include
- URL Preview Boolean to enable/disable URL preview in the notification
- Sound Boolean to enable/disable playing a notification sound
- Push Boolean to enable/disable sending a push notification
- Email Boolean to enable/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 Number offset for pagination when retrieving notifications
- Filter JSON object specifying filter criteria
- Order JSON object specifying sort order

Output

The node outputs an array of items, each containing a json field representing the result of the operation. For the "Mark as Unread" operation, the output typically includes confirmation data from Bitrix24 indicating the notification was successfully marked as unread.

If an error occurs and the node is configured to continue on failure, the output will contain an item with an error message, the resource name, and a timestamp.

No binary data output is indicated for this operation.

Dependencies

  • Requires authentication credentials for Bitrix24 via one of the supported methods: OAuth2, webhook URL, or API key.
  • The node depends on Bitrix24's API endpoints to perform notification operations.
  • No additional external services beyond Bitrix24 are required.
  • Proper configuration of authentication credentials in n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or expired authentication credentials causing authorization failures.
    • Incorrect or missing Notification ID leading to errors from the Bitrix24 API.
    • Network connectivity problems preventing API calls.
    • Malformed JSON in options like attachments or buttons causing request failures.

  • Error messages:

    • Errors returned from Bitrix24 API will be surfaced in the node output if "Continue On Fail" is enabled.
    • Typical errors include "Notification not found", "Unauthorized", or "Invalid parameters".

  • Resolutions:

    • Verify and refresh authentication credentials.
    • Ensure the Notification ID is correct and exists in the Bitrix24 account.
    • Validate JSON syntax in any JSON-type input fields.
    • Check network connectivity and firewall settings.

Links and References

Discussion