Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with the Gitea API to retrieve subscription information for a specific issue within a repository. It is useful when you want to programmatically access who is subscribed to notifications or updates on a particular issue in a Gitea-hosted project.

Common scenarios include:

  • Monitoring subscribers of an issue to send custom notifications.
  • Integrating issue subscription data into dashboards or reports.
  • Automating workflows based on issue subscription changes.

For example, you might use this node to fetch all users subscribed to issue #42 in the "my-repo" repository owned by "my-user" and then trigger alerts or sync subscriber lists with other systems.

Properties

Name Meaning
Owner The owner (user or organization) of the repository where the issue exists.
Repo The name of the repository containing the issue.
Index The index (number) of the issue for which subscriptions are being retrieved.
Page (Optional) The page number of results to return, starting at 1. Useful for pagination.
Limit (Optional) The number of results per page to return. Controls the page size of responses.

Output

The node outputs JSON data representing the list of subscribers to the specified issue. Each item in the output typically contains details about a subscriber such as their username and subscription status.

If the API supports it, the output may be paginated according to the Page and Limit parameters.

No binary data output is expected from this operation.

Dependencies

  • Requires a valid API key credential for authenticating with the Gitea instance.
  • Needs the base URL of the Gitea server configured in the credentials.
  • Relies on the Gitea REST API endpoint /api/v1/repos/{owner}/{repo}/issues/{index}/subscriptions or equivalent.

Troubleshooting

  • Invalid credentials or authentication errors: Ensure that the API key/token and base URL are correctly set in the node's credentials.
  • Issue not found: Verify that the Owner, Repo, and Index values correspond to an existing issue.
  • Pagination issues: If no results appear, check if the Page and Limit parameters are set correctly; remember pages start at 1.
  • API rate limits: If requests fail due to rate limiting, consider adding delays or using authenticated requests with higher limits.

Links and References

Discussion