Bitrix24 icon

Bitrix24

Interact with Bitrix24 CRM and business platform
Join our community

Actions290

Overview

The node integrates with the Bitrix24 platform, specifically providing functionality to confirm notifications within Bitrix24's notification system. This operation is useful in scenarios where automated workflows need to acknowledge or confirm receipt of notifications programmatically, such as confirming task assignments, alerts, or messages within a business process.

Practical examples include:

  • Automatically confirming a notification when a related CRM deal reaches a certain stage.
  • Confirming user notifications after processing them in an external system.
  • Integrating notification confirmation into multi-step automation flows to ensure proper tracking and acknowledgment.

Properties

Name Meaning
Authentication Method used to authenticate with Bitrix24. Options: OAuth2 (recommended for production), Webhook (simpler but less secure), API Key authentication.
Notification ID The unique identifier of the notification to confirm. Required to specify which notification is being confirmed.
Options Additional optional parameters to customize the confirmation behavior:
- Attachments JSON array specifying attachments to include with the confirmation.
- URL Preview Boolean indicating whether to show URL previews in the notification.
- Sound Boolean indicating whether to play a notification sound upon confirmation.
- 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 Custom text label for the confirm button.
- Decline Text Custom text label for the decline button.
- Offset Numeric offset for paginating through notifications (not typically relevant for confirmation but available).
- Filter JSON object defining filter criteria for selecting notifications (general option, not specific to confirmation).
- Order JSON object defining sort order for notifications (general option, not specific to confirmation).

Output

The node outputs an array containing one item per execution. Each item has a json field representing the response from Bitrix24 after attempting to confirm the notification. The structure typically includes:

  • Confirmation status or result details returned by Bitrix24.
  • In case of failure and if "Continue On Fail" is enabled, an error object with:
    • error: Error message string.
    • resource: The resource name ("notify").
    • timestamp: ISO timestamp of the error occurrence.

No binary data output is indicated for this operation.

Dependencies

  • Requires valid authentication credentials for Bitrix24 via one of the supported methods: OAuth2, webhook URL, or API key.
  • The node depends on Bitrix24's API endpoints for notification management.
  • No additional external services are required beyond Bitrix24 itself.
  • 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 about the notification not found.
    • Malformed JSON in options like attachments or buttons causing parsing errors.
    • Network connectivity issues preventing API calls to Bitrix24.

  • Error Messages:

    • Errors returned from Bitrix24 API will be surfaced in the output if "Continue On Fail" is enabled.
    • Typical error messages may include "Notification not found", "Unauthorized", or JSON parse errors.

  • Resolutions:

    • Verify and refresh authentication credentials.
    • Ensure the Notification ID is correct and exists in Bitrix24.
    • Validate JSON syntax in options fields before execution.
    • Check network connectivity and firewall settings.

Links and References

Discussion