GitLab API icon

GitLab API

Gitlab

Actions917

Overview

This node operation retrieves a specific GPG key of the authenticated user from the GitLab API (v4). It is useful for scenarios where you need to access details about a particular GPG key associated with the user's GitLab account, such as verifying key information or managing user security settings.

Use Case Examples

  1. Fetch details of a user's GPG key by providing the key ID to audit or verify the key's properties.
  2. Use in automation workflows to manage GitLab user security keys programmatically.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request, useful for public endpoints or testing.
Authentication Type of authentication used for the request, defaulting to GitLab API key authentication.
baseUrl Base URL of the GitLab instance to which the request is sent, defaulting to https://gitlab.com.
Method HTTP method used for the request, default is GET.
Path Parameters Parameters included in the request path, specifically the key_id which identifies the GPG key to retrieve.

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 the GPG key.
  • user_id - The ID of the user who owns the GPG key.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the key_id path parameter is provided and is a valid integer; missing or invalid key_id will cause request failure.
  • Authentication errors may occur if the GitLab API key credential is missing or invalid; verify credentials are correctly configured.
  • Network or baseUrl misconfiguration can lead to connection errors; confirm the baseUrl is correct and accessible.

Links

Discussion