Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node interacts with the Gitea API to list repositories associated with a specific team within an organization. It is useful for scenarios where you need to programmatically retrieve all repositories that a particular team has access to in a given organization on a Gitea instance. For example, it can be used to audit team repository access, automate reporting, or synchronize repository data with other systems.

Properties

Name Meaning
Id The numeric ID of the team whose repositories you want to list. This identifies the team within the organization.
Org The name of the organization that owns the repository. This specifies the organizational context for the request.
Repo The name of the repository to list. This targets a specific repository within the organization and team scope.

Output

The node outputs JSON data representing the list of repositories associated with the specified team in the organization. Each item in the output typically contains details about a repository such as its name, description, URL, and other metadata provided by the Gitea API.

If the node supports binary data output (not evident from the provided code), it would generally represent files or attachments related to the repositories, but this is not indicated here.

Dependencies

  • Requires an active connection to a Gitea instance via its API.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The base URL of the Gitea server must be set in the credentials configuration.
  • Uses the Gitea REST API endpoint /api/v1 to perform operations.

Troubleshooting

  • Invalid Team ID: If the team ID does not exist or is incorrect, the API will return an error or empty result. Verify the team ID is correct.
  • Authentication Errors: Missing or invalid API credentials will cause authorization failures. Ensure the API key/token is valid and has sufficient permissions.
  • Organization or Repository Not Found: If the organization or repository names are misspelled or do not exist, the node will fail to retrieve data.
  • Network Issues: Connectivity problems to the Gitea server will prevent the node from working. Check network access and server availability.
  • API Rate Limits: Excessive requests may trigger rate limiting; handle retries or backoff accordingly.

Links and References

Discussion