Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node operation retrieves a list of notifications from the connected service. It is useful for scenarios where you want to monitor or process notifications programmatically, such as fetching unread alerts, tracking pinned messages, or filtering notifications by time or subject type. For example, you could use this node to build a dashboard that displays recent notifications or automate workflows triggered by specific notification statuses.

Properties

Name Meaning
All If true, includes notifications marked as read; default is true (show all notifications).
Status Types Filters notifications by their status. Options include: unread, read, and/or pinned. Defaults to unread & pinned.
Subject Type Filters notifications by their subject type. Accepts JSON array of subject types to filter by.
Since Only show notifications updated after this timestamp (RFC 3339 format).
Before Only show notifications updated before this timestamp (RFC 3339 format).
Page The page number of results to return (1-based pagination).
Limit The number of notifications to return per page (page size).

Output

The output contains a JSON array of notification objects matching the query parameters. Each notification object typically includes details such as its status (read/unread/pinned), subject type, timestamps, and other metadata relevant to the notification. This allows downstream nodes or workflows to process or display these notifications accordingly.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API authentication token or key configured in the node credentials to access the notification service.
  • The node sends HTTP requests to the service's API endpoint, so network connectivity and proper base URL configuration are necessary.

Troubleshooting

  • Empty Results: If no notifications are returned, verify the filter parameters (status-types, since, before) to ensure they match existing notifications.
  • Invalid Timestamp Format: The since and before properties require RFC 3339 formatted timestamps. Incorrect formats may cause errors or empty responses.
  • Pagination Issues: Setting page or limit to zero or negative values might lead to unexpected behavior or errors. Use positive integers.
  • Authentication Errors: Ensure the API authentication token is valid and has sufficient permissions to read notifications.
  • API Rate Limits: Frequent calls may hit rate limits imposed by the service, resulting in errors or throttling.

Links and References

  • RFC 3339 Timestamp Format
  • Refer to your service's official API documentation for detailed information on notification endpoints and parameters.

Discussion