Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with the Gitea API to retrieve information about a specific release in a repository by its tag name. It is useful when you want to programmatically fetch details of a particular release version identified by a tag, such as release notes, assets, or metadata.

Common scenarios include:

  • Automating deployment pipelines that need to verify or use release information.
  • Integrating release data into dashboards or notifications.
  • Fetching release details for audit or compliance purposes.

For example, you can use this node to get the release information tagged "v1.0.0" from a repository owned by "octocat" named "hello-world".

Properties

Name Meaning
Owner The owner (user or organization) of the repository.
Repo The name of the repository.
Tag The tag name of the release to retrieve.

Output

The node outputs JSON data representing the release associated with the specified tag. This typically includes fields such as release ID, tag name, release name, description/body, creation date, published date, author information, and any attached assets or binaries related to the release.

If the release contains binary assets, those are usually referenced in the JSON output but not directly output as binary data by the node.

Dependencies

  • Requires an API key credential for authenticating with the Gitea instance.
  • Needs the base URL of the Gitea server configured in the credentials.
  • Depends on the Gitea REST API being accessible and the user having permission to read repository releases.

Troubleshooting

  • Common issues:

    • Incorrect owner, repo, or tag values will result in errors or empty responses.
    • Network connectivity problems or incorrect base URL configuration can cause request failures.
    • Insufficient permissions or invalid API credentials will lead to authentication errors.
  • Error messages:

    • 404 Not Found: The specified release tag does not exist in the repository. Verify the tag name and repository details.
    • 401 Unauthorized: Authentication failed. Check the API key and credential setup.
    • Network errors: Ensure the Gitea server URL is correct and reachable from n8n.

Links and References

Discussion