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 enables interaction with GitLab groups, specifically supporting the deletion of a group by its numeric ID. It is useful in automation workflows where managing GitLab groups programmatically is required, such as cleaning up unused groups or integrating group management into CI/CD pipelines.
For example, you can use this node to delete a specific GitLab group by providing its Group ID, automating administrative tasks without manual intervention in the GitLab UI.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose between using saved credentials ("Credential") or specifying 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 authentication. 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. |
| Group ID | (Required) Numeric ID of the group to delete. Must be a positive integer (minimum 1). |
Output
The node outputs JSON data representing the response from the GitLab API after attempting to delete the specified group. Typically, a successful deletion returns an empty response or confirmation status. If the deletion fails, error information will be included in the output.
No binary data output is produced by this operation.
Dependencies
- Requires access to a GitLab instance, either the public GitLab server or a self-hosted GitLab server.
- Requires an API access token with sufficient permissions to delete groups.
- The node supports two authentication modes:
- Using saved credentials configured in n8n.
- Providing custom connection details including server URL and personal access token directly in the node parameters.
Troubleshooting
- Invalid Group ID: The Group ID must be a positive integer. Providing zero or negative values will cause validation errors.
- Insufficient Permissions: The access token used must have permission to delete groups. Otherwise, the API will return authorization errors.
- Group Not Found: If the specified Group ID does not exist, the API will return a not found error.
- Network Issues: Ensure that the GitLab server URL is reachable and correct, especially when using custom authentication.
- Error Messages: Common error messages include:
- "Unauthorized" – Check the access token validity and permissions.
- "Not Found" – Verify the Group ID exists.
- "Bad Request" – Confirm all required parameters are correctly set.
Resolving these typically involves verifying the input parameters, ensuring proper API token scopes, and confirming network connectivity.