GitLab API icon

GitLab API

Gitlab
Join our community

Actions880

Overview

This node operation retrieves the GPG keys associated with the authenticated user from the GitLab API (version 4). It is useful for scenarios where you need to manage or verify the user's GPG keys programmatically, such as in automation workflows for security audits or user profile management.

Use Case Examples

  1. Fetch the list of GPG keys for the current user to verify which keys are active.
  2. Automate the retrieval of user GPG keys to sync with another system or database.

Properties

Name Meaning
Skip Authentication If set to true, the node will skip using authentication for the request.
baseUrl The base URL of the GitLab instance to which the API requests are sent.
Method The HTTP method used for the API request (GET, POST, PUT, DELETE, HEAD, PATCH).
Query Parameters Optional query parameters to control pagination of the GPG keys list.

Output

JSON

  • id - The unique identifier of the GPG key.
  • key - The actual GPG public key string.
  • created_at - Timestamp when the GPG key was created.
  • expires_at - Timestamp when the GPG key expires, if applicable.
  • can_edit - Boolean indicating if the user can edit this GPG key.
  • can_delete - Boolean indicating if the user can delete this GPG key.

Dependencies

  • GitLab API authentication token

Troubleshooting

  • Ensure the GitLab API credentials are correctly configured and have the necessary permissions to access user GPG keys.
  • If the API returns an authentication error, verify that the 'Skip Authentication' option is not enabled unless intended.
  • Check the base URL to ensure it points to the correct GitLab instance, especially if using a self-hosted GitLab server.
  • Pagination parameters (page and per_page) should be valid integers; invalid values may cause API errors.

Links

Discussion