GiteaInstall

Overview

This node interacts with the Gitea API to retrieve information about a user's GPG key. Specifically, the "User Current Get GPG Key" operation fetches details of a GPG key associated with the currently authenticated user by its unique identifier. This is useful in scenarios where you need to verify or manage cryptographic keys linked to a user account, such as for signing commits or verifying identity in version control workflows.

Practical examples include:

• Automating retrieval of a user's GPG key details to display or audit them.
• Integrating with CI/CD pipelines that require verification of commit signatures.
• Managing user security settings programmatically within an organization using Gitea.

Properties

Output

The node outputs JSON data representing the details of the requested GPG key. This typically includes fields such as the key ID, public key content, creation and expiration dates, and any associated metadata provided by the Gitea API.

No binary data output is involved in this operation.

Dependencies

• Requires an API authentication token credential to connect securely to 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 authenticated user having permission to view their GPG keys.

Troubleshooting

• Common issues:

  • Invalid or missing API credentials will cause authentication failures.
  • Providing an incorrect or non-existent GPG key ID will result in errors or empty responses.
  • Network connectivity problems to the Gitea server can prevent successful API calls.

• Error messages and resolutions:

  • 401 Unauthorized: Check that the API token is valid and has sufficient permissions.
  • 404 Not Found: Verify that the GPG key ID exists for the current user.
  • Network errors: Ensure the Gitea server URL is correct and reachable from n8n.

Links and References

• Gitea API Documentation - User GPG Keys
• Gitea Official Website