GitLab API

GitlabTool

Actions905

Overview

This node operation retrieves audit events for a specific project from the GitLab API (v4). It is useful for monitoring and auditing changes or activities within a GitLab project, such as tracking user actions or system events. Practical examples include compliance auditing, security monitoring, and activity logging for project management.

Use Case Examples

  1. Retrieve audit events created after a specific date to monitor recent changes.
  2. Fetch audit events within a date range to analyze project activity over time.
  3. Paginate through audit events to process or display them in batches.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the request.
Authentication The authentication method used for the request, typically an API key credential.
baseUrl The base URL of the GitLab instance to which the request is sent.
Method The HTTP method used for the request, default is GET.
Query Parameters Optional query parameters to filter and paginate audit events.
Path Parameters Path parameters specifying the project ID to retrieve audit events for.

Output

JSON

  • id - The unique identifier of the audit event.
  • author_id - The ID of the user who performed the action.
  • entity_id - The ID of the entity affected by the audit event.
  • entity_type - The type of entity affected by the audit event.
  • details - Details about the audit event.
  • ip_address - IP address from which the action was performed.
  • created_at - Timestamp when the audit event was created.

Dependencies

  • GitLab API authentication token or API key credential

Troubleshooting

  • Ensure the project ID is valid and accessible with the provided authentication.
  • Verify that the base URL is correct and reachable.
  • Check that the authentication token or API key has sufficient permissions to access audit events.
  • Handle pagination properly to retrieve all audit events if there are many.
  • Common error messages include 401 Unauthorized (invalid or missing authentication), 404 Not Found (invalid project ID), and 400 Bad Request (invalid query parameters).

Links

Discussion