Actions66
- Branch Actions
- File Actions
- Group Actions
- Issue Actions
- Merge Request Actions
- Pipeline Actions
- Project Actions
- Raw API Actions
- Release Actions
- Tag Actions
Overview
This node operation deletes a specific pipeline in a GitLab project. Pipelines in GitLab represent automated workflows such as CI/CD processes triggered by code changes. Deleting a pipeline can be useful to clean up old or erroneous pipelines, manage resource usage, or remove pipelines that are no longer relevant.
Typical use cases include:
- Automatically removing failed or obsolete pipelines after certain conditions.
- Managing pipeline lifecycle programmatically within automation workflows.
- Integrating with other systems to maintain a clean state of CI/CD pipelines.
For example, you might configure this node to delete a pipeline by specifying the project and pipeline ID, helping automate cleanup tasks in your DevOps process.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose whether to use saved credentials ("Credential") or provide custom connection details ("Custom") for accessing the GitLab API. |
| GitLab Server | Base URL of your GitLab instance, e.g., "https://gitlab.com". Only shown if using Custom authentication. Defaults to "https://gitlab.com". |
| Access Token | Personal access token with API permissions for authenticating API requests. 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 delete. Must be a positive integer. This is a required property. |
Output
The node outputs JSON data representing the response from the GitLab API after attempting to delete the specified pipeline. Typically, deleting a pipeline returns an empty response or confirmation status. The output will contain metadata about the execution and any returned data from the API call.
No binary data output is involved in this operation.
Dependencies
- Requires access to a GitLab instance (either gitlab.com or a self-hosted server).
- Requires an API access token with sufficient permissions to delete pipelines in the target project.
- If using saved credentials, those must be configured in n8n with appropriate API keys or tokens.
- No additional external dependencies beyond standard HTTP API calls to GitLab.
Troubleshooting
- Invalid or missing Pipeline ID: Ensure the Pipeline ID is a positive number and corresponds to an existing pipeline in the project.
- Authentication errors: Verify that the access token or credentials have the necessary API permissions to delete pipelines.
- Project identification issues: If using custom authentication, ensure that either Project ID is set or both Project Owner and Project Name are correctly specified.
- API rate limits or network errors: Check connectivity to the GitLab server and confirm you are not exceeding API rate limits.
- Error messages from GitLab API: These may indicate permission issues, non-existent resources, or invalid parameters. Review the error message details and adjust inputs accordingly.