Actions18
- Branch Actions
- File Actions
- Issue Actions
- Merge Request Actions
- Pipeline Actions
- Raw API Actions
Overview
This node integrates with GitLab to perform extended operations on various GitLab resources. Specifically, for the Pipeline - Get operation, it fetches detailed information about a single pipeline identified by its numeric ID within a GitLab project.
Typical use cases include:
- Retrieving the status and details of a specific pipeline run in a CI/CD workflow.
- Monitoring pipeline progress or results programmatically.
- Integrating pipeline data into automated workflows for reporting or triggering subsequent actions.
For example, you might use this node to get the pipeline with ID 42 to check if it succeeded before deploying an application.
Properties
| Name | Meaning |
|---|---|
| Pipeline ID | Numeric ID of the pipeline to retrieve, e.g., 42. This identifies which pipeline to fetch. |
Output
The node outputs JSON data representing the pipeline details as returned by the GitLab API. This typically includes fields such as pipeline status, stages, commit info, timestamps, and other metadata related to the pipeline execution.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with GitLab.
- The node expects configuration of the GitLab project context either via project ID or project owner/name credentials.
- Uses internal helper functions to make authenticated HTTP requests to GitLab's REST API.
Troubleshooting
Common issues:
- Invalid or missing pipeline ID will cause the request to fail.
- Incorrect or missing GitLab API credentials will result in authentication errors.
- If the project context (ID or owner/name) is not properly set in credentials, the API endpoint cannot be constructed correctly.
Error messages:
- "Unknown resource" error indicates the selected resource is not supported.
- HTTP errors from GitLab (e.g., 404 Not Found) usually mean the pipeline ID does not exist or is inaccessible.
Resolutions:
- Verify the pipeline ID is correct and exists in the target project.
- Ensure the API key credential has sufficient permissions to read pipelines.
- Confirm that project identification details are correctly configured in the node credentials.