Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node operation fetches a list of notifications for a specific repository in Gitea. It allows users to retrieve notifications filtered by various criteria such as read status, subject type, and update timestamps. This is useful for monitoring activity or updates on repositories, enabling automation workflows that react to new notifications or changes.

Practical examples:

  • Automatically fetching unread notifications from a repo to trigger alerts or further processing.
  • Retrieving all notifications including read ones for audit or reporting purposes.
  • Filtering notifications by subject type (e.g., issues, pull requests) to focus on relevant events.

Properties

Name Meaning
Owner The owner of the repository whose notifications you want to fetch.
Repo The name of the repository to get notifications from.
All Boolean flag to include notifications marked as read (true) or only unread ones (false). Default is true.
Status Types JSON array specifying which notification statuses to include: unread, read, and/or pinned. Defaults to unread & pinned.
Subject Type JSON array to filter notifications by their subject type (e.g., issue, pull request).
Since Timestamp (RFC 3339 format) to show notifications updated after this time.
Before Timestamp (RFC 3339 format) to show notifications updated before this time.
Page Number indicating the page of results to return (1-based pagination).
Limit Number indicating the maximum number of results per page.

Output

The output contains a JSON array of notification objects retrieved from the specified repository. Each notification object typically includes details such as the notification's ID, repository info, subject, status (read/unread/pinned), and timestamps.

If binary data were involved (not indicated here), it would represent attachments or related files, but this operation focuses solely on JSON notification data.

Dependencies

  • Requires an API key credential for authenticating with the Gitea instance.
  • Needs the base URL of the Gitea server configured in credentials.
  • Depends on the Gitea API being accessible and the user having permission to access the repository notifications.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication errors.
    • Incorrect owner or repo names will result in "not found" or empty responses.
    • Improperly formatted timestamps for since or before parameters may cause request failures.
    • Pagination parameters (page and limit) set to zero or negative values might lead to unexpected results or errors.

  • Error messages:

    • Authentication errors: Verify the API key and base URL are correct and have sufficient permissions.
    • 404 Not Found: Check that the owner and repo names are accurate and the repository exists.
    • 400 Bad Request: Ensure query parameters like timestamps and JSON arrays are correctly formatted.

Links and References

Discussion