GitLab API icon

GitLab API

Gitlab
Join our community

Actions880

Overview

This node operation deletes a specific email address associated with the authenticated user in GitLab. It is useful for managing user email addresses by removing outdated or unwanted emails from the user's GitLab account. For example, a user might want to delete an old email address that they no longer use or that has been compromised.

Use Case Examples

  1. Deleting a user's secondary email address from their GitLab profile to maintain account security.
  2. Removing an email address that is no longer valid or accessible to keep the user's contact information up to date.

Properties

Name Meaning
Skip Authentication Determines whether to skip the authentication process for the API request.
Authentication Specifies the authentication method to use, defaulting to GitLab API authentication.
baseUrl The base URL for the GitLab instance, defaulting to https://gitlab.com.
Method The HTTP method to use for the request, default is GET but DELETE is used for this operation.
Path Parameters The path parameter 'email_id' specifies the ID of the email to be deleted.

Output

JSON

  • statusCode - HTTP status code of the delete operation response
  • responseBody - Response body returned from the GitLab API after attempting to delete the email

Dependencies

  • GitLab API authentication token or credentials

Troubleshooting

  • Ensure the 'email_id' path parameter is correctly provided and corresponds to an existing email ID in the user's GitLab account.
  • Verify that the authentication credentials are valid and have sufficient permissions to delete user emails.
  • Common error messages include 401 Unauthorized (invalid or missing authentication), 404 Not Found (email ID does not exist), and 403 Forbidden (insufficient permissions). Resolving these involves checking credentials, permissions, and the correctness of the email ID.

Links

Discussion