GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation retrieves events for a specified user from the GitLab API (version 4). It is useful for monitoring user activities such as issues, merge requests, notes, and other event types within GitLab projects. For example, it can be used to fetch recent user events for auditing or activity tracking purposes.

Use Case Examples

  1. Fetch the latest 20 events for a user by their ID or username.
  2. Filter user events by action type or target type, such as only merge request events.
  3. Retrieve events created before or after a specific date to analyze user activity within a time range.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the API request.
Authentication The authentication method used for the API request, typically an API key credential.
baseUrl The base URL of the GitLab instance to send requests to, defaulting to https://gitlab.com.
Method The HTTP method to use for the request, default is GET.
Parameter Schema Defines the parameters for the API request including user ID, pagination, filtering by action, target type, date range, and sorting order.
Query Parameters Collection of optional query parameters such as page number, items per page, action filter, target type filter, date filters, and sort order.
Path Parameters Collection of path parameters including the user ID or username to specify which user's events to retrieve.

Output

JSON

  • ``
    • id - Unique identifier of the event.
    • action_name - Name of the action performed in the event.
    • target_type - Type of the target object related to the event.
    • created_at - Timestamp when the event was created.
    • author - Information about the user who triggered the event.
    • project_id - ID of the project related to the event.

Dependencies

  • GitLab API authentication credential

Troubleshooting

  • Ensure the user ID or username provided in path parameters is valid and exists in GitLab.
  • Verify that the API authentication token is correctly configured and has sufficient permissions to access user events.
  • Check the baseUrl if using a self-hosted GitLab instance to ensure it is correct.
  • If filtering parameters are used, confirm they match the allowed values (e.g., target_type must be one of the specified enums).
  • Pagination parameters (page, per_page) should be positive integers; invalid values may cause errors.

Links

Discussion