GitLab API

GitlabTool
Join our community

Actions1000

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, a user can fetch all events related to a project to track changes or updates over time.

Use Case Examples

  1. Fetch all events for a project with ID '123'.
  2. Filter project events to only include 'merge_request' target types.
  3. Retrieve events created after a specific date to monitor recent activity.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the request.
Authentication The authentication method used for the request, hidden if Skip Authentication is true.
baseUrl The base URL of the GitLab instance to send the request to.
Method HTTP method to use for the request (GET, POST, PUT, DELETE, HEAD, PATCH).
Query Parameters Optional filters and pagination parameters for the events request.
Path Parameters Path parameters including the project ID or URL-encoded path.

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 involved in the event (e.g., issue, merge_request).
  • author
    • username - The username of the event author.
  • created_at - The timestamp when the event was created.
  • project_id - The ID of the project associated with the event.

Dependencies

  • GitLab API authentication token or credentials

Troubleshooting

  • Ensure the project ID provided in the path parameters is correct and accessible with the authenticated user.
  • Verify that the base URL is correct and points to a valid GitLab instance.
  • Check that the authentication token has sufficient permissions to access project events.
  • If filtering by date or event type, ensure the parameters are correctly formatted and valid according to GitLab API specifications.

Links

Discussion