Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node interacts with the Gitea API to retrieve detailed information about a specific package hosted in a Gitea instance. It is useful when you need to programmatically access metadata or details of a package by specifying its owner, type, name, and version. Typical use cases include automation workflows that manage package dependencies, audit package versions, or integrate package data into other systems.

For example, you might use this node to fetch the exact version details of a package maintained by a particular user or organization on your Gitea server, enabling automated checks or deployment pipelines.

Properties

Name Meaning
Owner The username or organization that owns the package.
Type The category or type of the package (e.g., npm, maven, etc.).
Name The name identifier of the package.
Version The specific version number of the package to retrieve information for.

Output

The node outputs JSON data representing the package details as returned by the Gitea API. This typically includes metadata such as package description, version info, dependencies, publication date, and other relevant attributes depending on the package type.

If the package contains any binary data (e.g., package files), it would be handled accordingly, but based on the static code, the primary output is structured JSON describing the package.

Dependencies

  • Requires an active connection to a Gitea instance via its REST API.
  • Needs an API authentication token or key configured in the node credentials to authorize requests.
  • The base URL for the Gitea API must be set in the node credentials.
  • Uses the @devlikeapro/n8n-openapi-node package internally to build request properties from the OpenAPI specification.

Troubleshooting

  • Authentication errors: Ensure the API key or token provided has sufficient permissions to access package information.
  • Invalid parameters: Verify that the owner, type, name, and version fields are correctly filled and correspond to existing packages.
  • Network issues: Confirm that the Gitea server URL is reachable from the n8n environment.
  • API changes: If the Gitea API version changes, the node's OpenAPI spec may become outdated, causing failures; updating the node or its dependencies may be necessary.

Links and References

Discussion