Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node operation retrieves the list of GPG keys associated with the currently authenticated user in a Gitea instance. It is useful when you want to programmatically access or manage your GPG keys stored in Gitea, for example, to verify commit signatures or manage security settings.

Common scenarios include:

  • Automating audits of GPG keys linked to your user account.
  • Synchronizing GPG keys with other systems.
  • Displaying or processing GPG key information within workflows.

Properties

Name Meaning
Page The page number of results to return (1-based). Used for paginated responses to specify which page of results to fetch.
Limit The number of results per page (page size). Controls how many GPG keys are returned in one request.

Output

The output contains a JSON array of GPG key objects associated with the current user. Each object typically includes details such as the key ID, public key data, creation date, and other metadata relevant to the GPG key.

No binary data output is produced by this operation.

Dependencies

  • Requires an API authentication token credential configured in n8n to authenticate requests against the Gitea API.
  • The node uses the Gitea REST API endpoint /api/v1 as base URL, which must be correctly set in the credentials configuration.
  • No additional external services are required beyond the Gitea instance.

Troubleshooting

  • Empty results: If no GPG keys are returned, ensure that the authenticated user actually has GPG keys registered in Gitea.
  • Authentication errors: Verify that the API token or credentials used have sufficient permissions to read user GPG keys.
  • Pagination issues: If you expect more keys but only get partial results, adjust the Page and Limit properties accordingly.
  • API connectivity: Confirm that the Gitea instance URL is reachable and correct in the credentials setup.

Links and References

Discussion