Overview

This node interacts with the HumHub API to manage notifications, specifically allowing users to mark notifications as seen. It is useful in scenarios where users want to update the status of their notifications to indicate they have been viewed, helping to keep notification lists current and reduce clutter. For example, after processing notifications in an automated workflow, this node can mark them as seen to prevent repeated alerts.

Use Case Examples

1. Mark all unseen notifications as seen after processing them in a workflow.
2. Automatically update notification status to seen when a user reads them in an application.

Properties

Output

JSON

• id - The unique identifier of the notification.
• title - The title or summary of the notification.
• message - The detailed message content of the notification.
• seen - Boolean indicating whether the notification has been marked as seen.
• created_at - Timestamp when the notification was created.

Dependencies

• Requires authentication credentials: either Basic Auth credentials or a JWT Token for HumHub API access.

Troubleshooting

• Ensure the correct authentication method is selected and valid credentials are provided; otherwise, API requests will fail with authentication errors.
• If the node fails to mark notifications as seen, verify that the HumHub API endpoint '/notification/mark-as-seen' is accessible and the user has the necessary permissions.
• Common error messages include authentication failures, permission denied, or network connectivity issues. Check credentials, API endpoint URL, and network access to resolve these.

Links

• HumHub API Notifications Documentation - Official documentation for managing notifications via the HumHub API, including marking notifications as seen.