GitLab API icon

GitLab API

Gitlab
Join our community

Actions880

Overview

This node operation retrieves audit events for a specific group from the GitLab API (v4). It is useful for monitoring and auditing changes or activities within a GitLab group, such as tracking user actions or security-related events. For example, an administrator can use this node to fetch audit logs filtered by date or paginate through large sets of audit events.

Use Case Examples

  1. Fetch audit events created after a specific date to monitor recent changes in a group.
  2. Retrieve audit events for a group with pagination to review historical activities.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request, useful for public or unauthenticated access scenarios.
Authentication Type of authentication used, defaulting to GitLab API key authentication.
baseUrl Base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request, default is GET.
Query Parameters Optional query parameters to filter and paginate audit events.
Path Parameters Path parameters required for the request.

Output

JSON

  • id - Unique identifier of the audit event.
  • author_id - ID of the user who performed the action.
  • entity_id - ID of the entity affected by the audit event.
  • entity_type - Type of the entity affected (e.g., Group).
  • created_at - Timestamp when the audit event was created.
  • details - Details about the audit event, such as changes made.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the group ID path parameter is correctly set and is a valid integer.
  • Verify that the authentication credentials (GitLab API key) are correctly configured and have sufficient permissions to access group audit events.
  • Check the base URL if using a self-hosted GitLab instance to ensure it is correct.
  • If pagination parameters are used, ensure they are valid integers and within allowed ranges.
  • Common error messages include 401 Unauthorized (authentication issues), 404 Not Found (invalid group ID), and 400 Bad Request (invalid query parameters). Resolving these involves correcting credentials, verifying group existence, and validating input parameters.

Links

Discussion