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 manage various GitLab resources programmatically within n8n workflows. Specifically for the Pipeline - Create operation, this node enables users to trigger a new pipeline run on a specified branch or tag of a GitLab project.
This is useful in continuous integration and deployment (CI/CD) scenarios where you want to automate pipeline execution based on events or schedules. For example, after pushing code changes to a repository, you can use this node to start a pipeline that runs tests, builds artifacts, or deploys applications automatically.
Practical examples:
- Triggering a pipeline on the
mainbranch after merging a feature branch. - Starting a pipeline on a specific tag to build a release artifact.
- Automating pipeline runs as part of a larger workflow that includes notifications or deployments.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose between using saved credentials ("Credential") or providing 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. |
| Ref | Branch or tag that triggers the pipeline, such as main. Defaults to main. |
Output
The output JSON contains the response from the GitLab API after creating the pipeline. This typically includes details about the newly created pipeline such as:
- Pipeline ID
- Status (e.g., pending, running)
- Reference branch or tag
- User who triggered the pipeline
- Creation timestamp
- Other metadata related to the pipeline execution
No binary data is output by this operation.
Dependencies
- Requires an API token with appropriate permissions to create pipelines on the target GitLab project.
- Supports two authentication modes:
- Using saved credentials configured in n8n.
- Providing custom connection details including server URL and personal access token.
- The node uses GitLab's REST API endpoints to perform operations.
- No additional external dependencies beyond standard HTTP requests to GitLab.
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 may fail. Ensure correct project identification parameters.
- Authentication errors: If the access token lacks required API scopes or is invalid, the node will fail to authenticate. Verify token permissions and validity.
- Ref not found: Specifying a branch or tag (
ref) that does not exist in the project will cause the pipeline creation to fail. Confirm the ref exists. - API rate limits: Frequent pipeline creation requests might hit GitLab API rate limits. Consider adding delays or error handling for rate limit responses.
- Error messages: Errors returned from GitLab API are passed through. Common messages include unauthorized access, resource not found, or validation errors. Review the message for corrective action.