GitLab API

GitlabTool

Actions905

Overview

This node operation retrieves details of a specific user email by its ID from the GitLab API (v4). It is useful for scenarios where you need to fetch information about a particular email address associated with the authenticated user in GitLab, such as verifying email details or managing user contact information.

Use Case Examples

  1. Fetch details of a user email by providing the email ID to manage user contact information in GitLab.
  2. Verify a specific email address associated with the authenticated GitLab user.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request.
Authentication Type of authentication used, here it is GitLab API authentication.
baseUrl Base URL of the GitLab instance to which the request is sent.
Method HTTP method used for the request, default is GET.
Parameter Schema Schema defining the path parameter 'email_id' which is required and is an integer.
Request Body Schema Schema for the request body, null for this operation.
Request Path API endpoint path with a placeholder for the email ID.
Path Parameters Collection of path parameters, specifically 'email_id' which identifies the email to retrieve.

Output

JSON

  • id - The unique identifier of the email.
  • email - The email address.
  • confirmed_at - Timestamp when the email was confirmed.
  • created_at - Timestamp when the email was created.
  • is_primary - Boolean indicating if this email is the primary email.

Dependencies

  • GitLab API authentication

Troubleshooting

  • Ensure the 'email_id' path parameter is provided and is a valid integer; otherwise, the API will return an error.
  • If authentication is skipped, the request may fail due to lack of authorization.
  • Check the baseUrl to ensure it points to a valid GitLab instance.
  • Common error messages include 404 Not Found if the email ID does not exist, and 401 Unauthorized if authentication fails.

Links

Discussion