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 creating a new group in a GitLab instance. It is useful for automating the management of GitLab groups, such as organizing projects under specific teams or departments. For example, you can use this node to programmatically create groups for different development teams or client organizations, streamlining project access control and collaboration setup.
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 that takes precedence over owner and name. Used only if "Custom" authentication is selected. |
| Group Name | Required. The name of the new group to be created. |
| Group Path | Required. The URL path (slug) for the new group. |
| Parent ID | Numeric ID of the parent group under which the new group will be nested. Optional; defaults to 0 (no parent). |
Output
The node outputs JSON data representing the newly created group as returned by the GitLab API. This typically includes fields such as the group's ID, name, path, visibility settings, and other metadata about the group.
No binary data output is produced by this operation.
Dependencies
- Requires access to a GitLab instance, either the public https://gitlab.com or a self-hosted GitLab server.
- Requires an API access token with sufficient permissions to create groups on the GitLab instance.
- If using saved credentials, the node expects a configured API key credential within n8n.
- If using custom authentication, the user must provide the GitLab server URL and a valid personal access token.
Troubleshooting
- Invalid or missing access token: The node may fail if the provided token lacks the necessary API permissions or is invalid. Ensure the token has rights to create groups.
- Parent group ID issues: If specifying a parent group ID, ensure it exists and the token has permission to create subgroups.
- Group path conflicts: The group path must be unique within the GitLab instance. Conflicts will cause errors.
- API endpoint errors: Network issues or incorrect GitLab server URLs can cause request failures. Verify connectivity and URL correctness.
- Missing required parameters: Both "Group Name" and "Group Path" are mandatory. Omitting them will result in errors.