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 "GitLab Extended" node integrates with GitLab to perform various operations on GitLab resources. Specifically, the Pipeline - Get Jobs operation retrieves the list of jobs associated with a particular pipeline in a GitLab project.
This operation is useful when you want to monitor or analyze the individual jobs that make up a pipeline run, such as checking job statuses, durations, or logs. For example, it can be used to automate reporting on CI/CD pipelines, trigger alerts based on job outcomes, or gather metrics for performance analysis.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose whether to use saved credentials ("Credential") or provide custom connection details ("Custom"). |
| GitLab Server | Base URL of your GitLab instance (e.g., https://gitlab.com). Only shown if using Custom authentication. |
| Access Token | Personal access token with API permissions for GitLab. Only shown if using Custom authentication. |
| Project Owner | Namespace or owner of the project. Ignored if Project ID is set. Only shown if using Custom authentication. |
| Project Name | Project slug or name. Ignored if Project ID is set. Only shown if using Custom authentication. |
| Project ID | Numeric project ID. Takes precedence over owner and name if provided. Only shown if using Custom authentication. |
| Pipeline ID | Numeric ID of the pipeline to get jobs from. Must be a positive number. Required. |
| Return All | Whether to return all jobs or limit the number of results. Optional, defaults to false. |
| Limit | Maximum number of jobs to return if "Return All" is false. Minimum value is 1, default is 50. |
Output
The output is an array of JSON objects representing the jobs of the specified pipeline. Each job object typically contains details such as:
- Job ID
- Status (e.g., success, failed, running)
- Stage name
- Name of the job
- Duration
- Created and finished timestamps
- Other metadata related to the job execution
If binary data were involved (e.g., downloading artifacts), it would be summarized accordingly, but this operation returns only JSON job details.
Dependencies
- Requires access to a GitLab instance, either the public GitLab.com or a self-hosted GitLab server.
- Requires an API access token with appropriate permissions to read pipeline jobs.
- The node supports two authentication modes: using stored credentials or providing custom connection parameters directly.
- No additional external dependencies beyond standard HTTP requests to GitLab's REST API.
Troubleshooting
- Invalid Pipeline ID: If the pipeline ID is missing or not positive, the node will throw an error. Ensure the pipeline ID is correctly set and valid.
- Authentication Errors: Using invalid or expired access tokens will cause authorization failures. Verify the token has sufficient API scope and is active.
- Project Identification Issues: When using custom authentication, if both Project ID and Project Owner/Name are missing or incorrect, the request will fail. Prefer specifying the numeric Project ID.
- API Rate Limits: Frequent calls may hit GitLab API rate limits, resulting in errors or throttling. Consider enabling "Return All" carefully or limiting the number of requests.
- Network Connectivity: Ensure the GitLab server URL is reachable from the n8n environment.