Actions66
- Branch Actions
- File Actions
- Group Actions
- Issue Actions
- Merge Request Actions
- Pipeline Actions
- Project Actions
- Raw API Actions
- Release Actions
- Tag Actions
Overview
The node "GitLab Extended" provides extended integration with GitLab, allowing users to interact with various GitLab resources such as branches, pipelines, tags, releases, groups, projects, issues, merge requests, files, and raw API endpoints. Specifically, the Pipeline - Get operation fetches detailed information about a specific pipeline in a GitLab project by its numeric ID.
This node is beneficial for automating CI/CD workflows, monitoring pipeline statuses, or integrating pipeline data into other automation processes. For example, you can use it to retrieve the status and details of a pipeline triggered on a particular branch or commit, enabling conditional logic based on pipeline success or failure.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose how to authenticate: either using saved credentials ("Credential") or providing custom fields ("Custom"). |
| GitLab Server | Base URL of your GitLab instance, e.g., https://gitlab.com. Used only if "Custom" authentication is selected. |
| Access Token | Personal access token with API permissions for GitLab. Used only if "Custom" authentication is selected. |
| Project Owner | Namespace or owner of the project. Ignored if "Project ID" is set. Used only if "Custom" authentication is selected. |
| Project Name | Project slug or name. Ignored if "Project ID" is set. Used only if "Custom" authentication is selected. |
| Project ID | Numeric project ID. Takes precedence over owner and name if provided. Used only if "Custom" authentication is selected. |
| Pipeline ID | Required. Numeric ID of the pipeline to retrieve (must be positive). Default is 1. |
Output
- The output JSON contains the detailed information of the requested pipeline as returned by the GitLab API.
- This includes fields such as pipeline status, ref (branch or tag), SHA, user who triggered it, stages, jobs, timestamps, and more.
- The node does not output binary data for this operation.
Dependencies
- Requires an API authentication token with appropriate permissions to access the GitLab project and pipelines.
- Supports two authentication modes:
- Using saved credentials configured in n8n.
- Providing custom connection details including server URL and personal access token.
- No additional external dependencies beyond standard HTTP requests to the GitLab API.
Troubleshooting
- Invalid or missing Pipeline ID: The pipeline ID must be a positive number. If invalid, the node will throw an error.
- Authentication errors: Ensure that the provided access token or saved credentials have sufficient API permissions to read pipeline data.
- Project identification issues: When using custom authentication, if both Project ID and Project Owner/Name are empty or incorrect, the request will fail. Prefer using Project ID for accuracy.
- API rate limits: Frequent calls may hit GitLab API rate limits; consider adding delays or caching results.
- Network or server errors: Verify the GitLab server URL is correct and accessible from the n8n environment.