GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node operation retrieves events for a specific project from the GitLab API (v4). It is useful for monitoring project activities such as issues, merge requests, notes, and other event types. For example, it can be used to fetch recent events on a project to track changes or user actions.

Use Case Examples

  1. Fetch all events for a project by its ID.
  2. Filter project events by action type or target type (e.g., issues or merge requests).
  3. Retrieve events created before or after a specific date.
  4. Paginate through project events with page and per_page parameters.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the request.
Authentication The authentication method used, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance to connect to, defaulting to https://gitlab.com.
Method The HTTP method to use for the request, defaulting to GET.
Parameter Schema Defines the parameters for the API call including path and query parameters such as project ID, action filter, target type, date filters, sorting, and pagination.
Query Parameters Collection of optional query parameters to filter and paginate the events, including action, target_type, before, after, sort, page, and per_page.
Path Parameters Collection of path parameters, specifically the project ID or URL-encoded path to identify the project.

Output

JSON

  • id - The unique identifier of the event.
  • action_name - The name of the action performed in the event.
  • target_type - The type of the target object affected by the event (e.g., issue, merge_request).
  • author - Information about the user who triggered the event.
  • created_at - Timestamp when the event was created.
  • project_id - The ID of the project associated with the event.
  • details - Additional details about the event, if available.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the project ID or URL-encoded path is correctly provided; otherwise, the API call will fail.
  • Verify that the authentication credentials are valid and have sufficient permissions to access project events.
  • Check the baseUrl if connecting to a self-hosted GitLab instance to ensure it is correct.
  • If filtering by date, ensure the date format is correct (ISO 8601) to avoid errors.
  • Pagination parameters (page, per_page) should be positive integers; invalid values may cause errors or unexpected results.

Links

Discussion