GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation retrieves details of a specific trigger for a project in GitLab using the GitLab API. It is useful for scenarios where you need to programmatically access trigger information for CI/CD pipelines or automation workflows within a GitLab project. For example, you might use this node to fetch trigger details to verify or audit trigger configurations.

Use Case Examples

  1. Fetch trigger details for project ID 18 and trigger ID 10 to monitor CI/CD pipeline triggers.
  2. Retrieve trigger information to integrate with external automation tools that require trigger metadata.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request, useful for public or unauthenticated API endpoints.
Authentication Select the authentication method, 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 API request, default is GET.
Path Parameters Parameters to specify the project ID and trigger ID for the API request.

Output

JSON

  • id - The ID of the trigger.
  • description - Description of the trigger.
  • token - The token associated with the trigger.
  • created_at - Timestamp when the trigger was created.
  • updated_at - Timestamp when the trigger was last updated.
  • owner
    • id - ID of the owner of the trigger.
    • name - Name of the owner of the trigger.
    • username - Username of the owner of the trigger.
    • state - State of the owner (e.g., active, blocked).
    • avatar_url - URL to the avatar image of the owner.
    • web_url - URL to the web profile of the owner.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the project ID and trigger ID are correctly specified and exist in the GitLab instance.
  • Verify that the GitLab API key credential has sufficient permissions to access project triggers.
  • If skipping authentication, confirm that the GitLab instance allows unauthenticated access to the trigger endpoint.
  • Check the base URL to ensure it points to the correct GitLab instance, especially if using a self-hosted GitLab server.

Links

Discussion