Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node operation retrieves a list of the current user's keys from a Gitea instance via its API. It is useful for scenarios where you want to programmatically access SSH or GPG keys associated with the authenticated user, such as managing access credentials or auditing key usage.

Practical examples include:

  • Automating the retrieval of all SSH keys linked to your user account.
  • Filtering keys by fingerprint to check if a specific key is registered.
  • Paginating through large sets of keys when a user has many.

Properties

Name Meaning
Fingerprint The fingerprint of a specific key to filter the results by.
Page The page number of results to return (1-based). Useful for paginating through keys.
Limit The number of results per page (page size). Controls how many keys are returned at once.

Output

The output JSON contains an array of key objects representing the current user's keys. Each object typically includes details such as the key's fingerprint, type, creation date, and other metadata provided by the Gitea API.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to a Gitea instance with appropriate API access.
  • Needs an API authentication token credential configured in n8n to authorize requests.
  • The base URL for the Gitea API must be set in the node credentials.

Troubleshooting

  • Empty results: If no keys are returned, verify that the authenticated user actually has keys registered and that the fingerprint filter (if used) matches an existing key.
  • Authentication errors: Ensure the API token is valid and has sufficient permissions to read user keys.
  • Pagination issues: If you receive incomplete results, adjust the Page and Limit properties to navigate through all available keys.
  • API connectivity: Confirm the Gitea instance URL is correct and reachable from the n8n environment.

Links and References

Discussion