GitLab API

GitlabTool
Join our community

Actions905

Overview

This node interacts with the GitLab API to retrieve details about a specific release asset link within a project. It is useful for scenarios where you need to programmatically access metadata or information about release assets linked to a particular release tag in a GitLab project. For example, it can be used to fetch download URLs or descriptions of release assets for automation or integration workflows.

Use Case Examples

  1. Fetch details of a release asset link by specifying the project ID, release tag name, and link ID to automate release management.
  2. Integrate with CI/CD pipelines to verify or log release asset information before deployment.

Properties

Name Meaning
Skip Authentication Option to bypass authentication for the request.
Authentication Type of authentication used for the request, defaulting to GitLab API key.
baseUrl Base URL of the GitLab instance, default is https://gitlab.com.
Method HTTP method used for the API request.
Parameter Schema Defines required path parameters for the API call: project ID, release tag name, and link ID.
Request Body Schema Schema for the request body, null for this operation as it is a GET request.
Request Path API endpoint path template for the request.
Path Parameters Collection of path parameters including project ID, release tag name, and link ID to specify the resource.

Output

JSON

  • id - The ID of the release asset link.
  • name - The name of the release asset link.
  • url - The URL of the release asset link.
  • direct_asset_url - Direct URL to the asset file.
  • link_type - Type of the link (e.g., other, runbook).
  • created_at - Timestamp when the link was created.
  • updated_at - Timestamp when the link was last updated.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the project ID, tag name, and link ID are correctly specified and URL-encoded if necessary.
  • Authentication errors may occur if the GitLab API key is missing or invalid; verify credentials are correctly configured.
  • API rate limits or permission issues may cause request failures; check GitLab user permissions and API usage limits.

Links

Discussion