Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with the Gitea API to retrieve a specific deploy key from a repository. It is useful when you need to programmatically access details about a particular SSH key associated with a repository, for example, to verify its existence, check permissions, or audit keys.

A practical scenario would be automating repository management tasks where you want to fetch information about a deploy key by its ID without manually browsing the repository settings in the Gitea web interface.

Properties

Name Meaning
Owner The username or organization that owns the repository.
Repo The name of the repository from which to get the key.
Id The numeric identifier of the deploy key to retrieve.

Output

The node outputs JSON data representing the deploy key object retrieved from the Gitea API. This typically includes details such as the key's ID, title, key string, creation date, and whether it has read/write access.

No binary data output is involved.

Dependencies

  • Requires an API authentication token credential for Gitea.
  • Needs the base URL of the Gitea instance configured in the credentials.
  • Depends on the Gitea REST API being accessible and the user having permission to read deploy keys for the specified repository.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication errors.
    • Incorrect owner, repo, or key ID values will result in "not found" errors.
    • Insufficient permissions may lead to authorization errors.
  • Error messages:

    • 404 Not Found: Check if the owner, repo, and key ID are correct.
    • 401 Unauthorized: Verify that the API token is valid and has necessary scopes.
    • Network errors: Ensure the Gitea server URL is reachable from n8n.

Links and References

Discussion