Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node operation retrieves a list of activity feeds related to a specific user from a Gitea instance. It is useful for monitoring or auditing user actions within a Gitea repository hosting environment. For example, you can use it to track what activities a particular user has performed on a given date or to paginate through their activity history.

Properties

Name Meaning
Username The username of the user whose activity feeds you want to retrieve.
Only Performed By Boolean flag indicating whether to show only actions performed by the specified user (true) or include other related activities (false).
Date The specific date for which to find activities.
Page The page number of results to return, starting at 1.
Limit The number of results to return per page (page size).

Output

The output contains JSON data representing the user's activity feeds as returned by the Gitea API. Each item in the output corresponds to an individual activity event associated with the user, including details such as action type, timestamp, and related entities. There is no indication that binary data is returned by this operation.

Dependencies

  • Requires connection to a Gitea instance via its REST API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The base URL for the Gitea API must be set in the node's credential configuration.

Troubleshooting

  • Common issues:
    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect username or date format may result in empty or error responses.
    • Pagination parameters (page and limit) set to zero or negative values might not behave as expected; ensure they are positive integers.
  • Error messages:
    • Authentication errors typically indicate invalid or expired API tokens; reconfigure credentials.
    • "User not found" errors suggest the username does not exist in the Gitea instance.
    • Rate limiting errors may occur if too many requests are made in a short time; implement retries or backoff.

Links and References

Discussion