Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with a Gitea instance to list activity feeds for a specific repository. It is useful for monitoring repository events such as commits, issues, pull requests, and other activities on a given date or within paginated results. Practical applications include automating notifications about repository changes, auditing repository activity, or integrating repository event data into workflows.

Properties

Name Meaning
Owner The owner of the repository whose activity feeds you want to retrieve.
Repo The name of the repository for which to list activity feeds.
Date (Optional) The specific date to filter activities by.
Page (Optional) The page number of results to return, starting at 1.
Limit (Optional) The number of results per page to return (page size).

Output

The node outputs JSON data representing the activity feeds of the specified repository. This includes details about various repository events occurring on the specified date or within the requested page and limit parameters. The output structure typically contains an array of activity feed objects, each describing an event such as commits, issue updates, or pull request actions.

No binary data output is indicated.

Dependencies

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

Troubleshooting

  • Common Issues:

    • Incorrect or missing repository owner or name will result in errors or empty results.
    • Invalid date format may cause the API to reject the request.
    • Pagination parameters (page, limit) set to zero or negative values might not behave as expected.
    • Network connectivity or authentication failures can prevent successful API calls.
  • Error Messages:

    • Authentication errors indicate invalid or missing API credentials; verify and update the API key/token.
    • "Not Found" errors usually mean the repository or owner does not exist or is inaccessible.
    • Rate limiting errors from the Gitea API require waiting or adjusting request frequency.

Links and References

Discussion