GitLab API

GitlabTool

Actions905

Overview

This node operation retrieves details of a specific trigger token for a project in GitLab using the GitLab API v4. It is useful for automation workflows that need to access or verify trigger tokens associated with GitLab projects, such as CI/CD pipeline triggers or webhook configurations.

Use Case Examples

  1. Fetch trigger token details for project ID 18 and trigger ID 10 to verify or audit trigger configurations.
  2. Use in a workflow to dynamically retrieve trigger information before executing further GitLab API calls.

Properties

Name Meaning
Skip Authentication If set to true, the node will skip using authentication for the API request.
Authentication The authentication method used for the API request, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance to which the API request is sent, default is https://gitlab.com.
Method The HTTP method used for the API request, default is GET.
Path Parameters The path parameters required for the API endpoint, including the project ID and the trigger token ID.

Output

JSON

  • id - The project ID or URL-encoded path used in the request.
  • trigger_id - The trigger token ID used in the request.
  • response - The JSON response from the GitLab API containing details about the specified trigger token.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the project ID and trigger token ID are correctly specified and URL-encoded if necessary.
  • 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, which is uncommon.
  • Common error messages include 404 Not Found if the project or trigger ID does not exist, and 401 Unauthorized if authentication fails.

Links

Discussion