Actions11
Overview
This node interacts with GitLab to perform extended operations on various GitLab resources, including pipelines. Specifically, the Pipeline - Get Many operation retrieves multiple pipeline records from a specified GitLab project.
Use cases include:
- Fetching all or a limited number of pipelines for a project to monitor CI/CD status.
- Integrating pipeline data into workflows for reporting or triggering downstream automation.
- Auditing pipeline runs by retrieving historical pipeline information.
For example, you might use this node to list the last 50 pipelines run on a project owned by "my-org" and named "my-repo" to analyze build success rates.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method to authenticate with GitLab: either using an Access Token or OAuth2 credentials. |
| Project Owner | The username or group name that owns the GitLab project (e.g., "my-org"). |
| Project Name | The repository/project name within the owner’s namespace (e.g., "my-repo"). |
| Return All | Whether to return all available pipeline results or limit the number returned. |
| Limit | Maximum number of pipeline results to return if not returning all (minimum 1, default 50). |
Output
The node outputs 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/tag), user who triggered it, timestamps, and other metadata as provided by GitLab's pipelines API.
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 endpoints.
- No additional external dependencies beyond standard n8n environment and configured GitLab credentials.
Troubleshooting
- Invalid Credentials: If authentication fails, verify that the access token or OAuth2 token has sufficient permissions to read pipelines in the target project.
- Project Not Found: Ensure the "Project Owner" and "Project Name" are correct and that the authenticated user has access rights.
- Rate Limits: GitLab API rate limits may cause errors when requesting many pipelines; consider enabling "Return All" cautiously.
- Incorrect Parameters: Providing invalid or empty values for required fields like owner or repository will cause errors.
- Unknown Resource Error: This occurs if the resource parameter is set incorrectly; ensure "pipeline" is selected for this operation.