Actions11
Overview
This node interacts with GitLab to perform extended operations on various GitLab resources, including pipelines. Specifically, the Pipeline - Get operation retrieves detailed information about a single pipeline within a specified GitLab project.
Typical use cases include:
- Fetching the status and details of a specific pipeline run in a CI/CD workflow.
- Monitoring pipeline progress or results programmatically.
- Integrating pipeline data into automation workflows for reporting or triggering subsequent actions.
For example, you might use this node to get the current state of a pipeline by its ID to decide whether to deploy an application or notify a team.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with GitLab: either "Access Token" or "OAuth2". |
| Project Owner | The username or group name that owns the GitLab project (URL-encoded internally). |
| Project Name | The repository name of the GitLab project. |
| Pipeline ID | The unique numeric identifier of the pipeline to retrieve. |
Output
The node outputs JSON data representing the pipeline object returned by the GitLab API. This includes fields such as:
id: Pipeline identifier.status: Current status of the pipeline (e.g., running, success, failed).ref: Branch or tag name the pipeline ran against.sha: Commit SHA associated with the pipeline.web_url: URL to view the pipeline in GitLab UI.- Other metadata like creation time, duration, user who triggered it, etc.
No binary data is output by this operation.
Dependencies
- Requires a valid GitLab API authentication credential, either an access token or OAuth2 token.
- The node uses internal helper functions to make REST API calls to GitLab's endpoints.
- No additional external dependencies beyond standard n8n environment and GitLab API access.
Troubleshooting
Common issues:
- Incorrect project owner or repository name can cause "404 Not Found" errors.
- Invalid or expired authentication tokens will result in authorization errors.
- Providing a non-existent pipeline ID will also return a "404 Not Found".
Error messages:
"Unknown resource: pipeline"— indicates the resource parameter was not set correctly.- HTTP errors from GitLab API are passed through; check the error message for details.
Resolutions:
- Verify project owner and repository names exactly match those in GitLab.
- Ensure the authentication token has sufficient permissions to read pipelines.
- Confirm the pipeline ID exists in the specified project.