Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node operation allows users to mark notifications on a specific repository in Gitea as read or change their status. It is useful for managing notification states programmatically, such as marking all notifications on a repo as read after processing them or filtering notifications by their current status and updating them accordingly.

Practical examples include:

  • Automatically marking all unread notifications on a repository as read after a daily review.
  • Changing the status of pinned notifications to read once they are no longer relevant.
  • Filtering notifications updated since a certain timestamp and marking them as read to keep notification counts accurate.

Properties

Name Meaning
Owner The owner of the repository whose notifications you want to update.
Repo The name of the repository whose notifications you want to update.
All If set to true, marks all notifications on this repository regardless of status. Default is false.
Status Types An array specifying which notification statuses to target (e.g., unread, read, pinned). Defaults to unread.
To Status The status to assign to the selected notifications (e.g., read). Defaults to "read".
Last Read At A timestamp indicating the last time notifications were checked; notifications updated since then will not be updated.

Output

The node outputs JSON data representing the result of the notification update operation. This typically includes confirmation of the notifications that were marked or any relevant response from the Gitea API. There is no binary output.

Dependencies

  • Requires an API key credential for authenticating with a Gitea instance.
  • The node communicates with the Gitea API endpoint configured via credentials.
  • Proper configuration of the base URL for the Gitea server is necessary.

Troubleshooting

  • Invalid Owner or Repo: Errors may occur if the specified repository owner or name does not exist or is inaccessible. Verify spelling and permissions.
  • Authentication Failures: Ensure the API key credential is valid and has sufficient permissions to modify notifications.
  • Incorrect Status Values: Using unsupported status types or to-status values may cause errors. Use only supported statuses like "unread", "read", or "pinned".
  • Timestamp Format Issues: The last_read_at property must be a valid ISO 8601 timestamp string; otherwise, the API may reject the request.

Links and References

Discussion