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" integrates with GitLab's API to manage various GitLab resources. Specifically, for the Pipeline resource with the Get Many operation, it retrieves a list of pipelines from a specified GitLab project. This operation is useful when you want to monitor or analyze multiple pipeline runs, such as fetching recent CI/CD pipeline statuses, durations, or results for reporting or automation purposes.
Practical examples include:
- Fetching all pipelines for a project to trigger notifications on failures.
- Retrieving a limited number of recent pipelines to display in dashboards.
- Automating cleanup or analysis workflows based on pipeline data.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose between using saved credentials ("Credential") or specifying custom connection details ("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. Default: 0 |
| Return All | Whether to return all pipeline results or limit the number of returned items. Default: false |
| Limit | Maximum number of pipeline results to return if "Return All" is false. Default: 50 |
Output
The output is an array of JSON objects representing pipelines retrieved from the GitLab project. Each object corresponds to one pipeline and contains detailed information as provided by the GitLab API, such as pipeline ID, status, ref (branch or tag), SHA, user who triggered it, duration, and timestamps.
If "Return All" is enabled, all available pipelines are fetched; otherwise, the number of pipelines is limited by the "Limit" property.
No binary data output is produced by this operation.
Dependencies
- Requires access to a GitLab instance, either the public
https://gitlab.comor a self-hosted GitLab server. - Requires an API access token with appropriate permissions to read pipelines from the target project.
- The node supports two authentication modes:
- Using saved credentials configured in n8n.
- Providing custom connection details directly in the node parameters.
- No additional external dependencies beyond standard HTTP requests to GitLab API.
Troubleshooting
Invalid or missing project identification:
If neither a valid project ID nor both project owner and project name are provided (when using custom authentication), the request will fail. Ensure that the project is correctly identified.Authentication errors:
Errors related to authentication usually indicate invalid or insufficient API tokens. Verify that the access token has the required scopes to read pipelines.API rate limits or network issues:
If many pipelines are requested with "Return All" enabled, the node may hit GitLab API rate limits or experience timeouts. Consider limiting the number of results or adding delays.Invalid parameter values:
For example, setting "Limit" below 1 will cause validation errors. Always provide positive integers where required.Error messages from the node:
"Unknown resource: pipeline"— indicates a misconfiguration of the resource parameter. Confirm that "pipeline" is selected as the resource."tagName must not be empty"— unrelated to this operation but may appear if other operations are misconfigured.