GitLab API icon

GitLab API

Gitlab

Actions880

Overview

This node operation retrieves the project deploy keys for a specific user from the GitLab API. It is useful for scenarios where you need to manage or audit deploy keys associated with a user's projects, such as in DevOps automation or security audits. For example, you can fetch all deploy keys for a user to verify access or automate key rotation.

Use Case Examples

  1. Fetch deploy keys for a user to audit project access keys.
  2. Automate retrieval of deploy keys for integration with other security tools.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request.
baseUrl The base URL of the GitLab instance to connect to.
Method HTTP method to use for the request (GET, POST, PUT, DELETE, HEAD, PATCH).
Query Parameters Optional query parameters for pagination.
Path Parameters Path parameters required for the API call.

Output

JSON

  • id - The unique identifier of the deploy key.
  • title - The title of the deploy key.
  • key - The SSH key content.
  • created_at - Timestamp when the deploy key was created.
  • can_push - Indicates if the deploy key has push access.
  • projects - List of projects associated with the deploy key.

Dependencies

  • GitLab API authentication token or credentials

Troubleshooting

  • Ensure the user_id path parameter is correctly set and corresponds to an existing user in GitLab.
  • Verify that the authentication credentials are valid and have sufficient permissions to access user deploy keys.
  • Check the baseUrl if connecting to a self-hosted GitLab instance to ensure it is correct.
  • Common error messages include 401 Unauthorized (authentication issues), 404 Not Found (invalid user_id or no deploy keys), and 403 Forbidden (insufficient permissions).

Links

Discussion