Actions18
- Branch Actions
- File Actions
- Issue Actions
- Merge Request Actions
- Pipeline Actions
- Raw API Actions
Overview
The node "GitLab Extended" integrates with GitLab to perform various operations on different GitLab resources. Specifically, for the Pipeline resource with the Get Many operation, it fetches a list of pipelines from a specified GitLab project.
This operation is useful when you want to retrieve multiple pipeline records for analysis, monitoring, or reporting purposes. For example, you might use this node to get recent pipelines triggered on a project to check their statuses or durations, or to automate workflows based on pipeline results.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all pipeline results or only up to a given limit. |
| Limit | Maximum number of pipeline results to return (used only if "Return All" is false). |
- Return All: If set to
true, the node will fetch all available pipelines without limiting the number. - Limit: When "Return All" is
false, this sets the maximum number of pipelines to retrieve (minimum 1).
Output
The output is an array of JSON objects representing pipelines retrieved from the GitLab API. Each object corresponds to one pipeline and contains details such as pipeline ID, status, ref (branch or tag), user who triggered it, timestamps, and other metadata provided by GitLab's pipelines API.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for GitLab with access to the target project.
- The node expects either a project ID or a combination of project owner and project name configured in the credentials to identify the GitLab project.
- Uses GitLab REST API endpoints under
/projects/{projectId}/pipelines.
Troubleshooting
Common issues:
- Incorrect or missing project identification in credentials (project ID or owner/name) will cause API requests to fail.
- Insufficient permissions on the GitLab API token may result in authorization errors.
- Setting "Return All" to true on projects with very large numbers of pipelines may lead to long execution times or rate limiting.
Error messages:
"Unknown resource: pipeline"— indicates the resource parameter was not correctly set to "pipeline".- API errors related to authentication or permissions should be resolved by verifying the API token and its scopes.
"The 'oldLine' parameter must be a non-negative number."is unrelated to this operation but may appear if parameters for other operations are misconfigured.