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's API to perform extended operations on various GitLab resources. Specifically, for the Group resource with the List Members operation, this node fetches the members of a specified GitLab group. This is useful in scenarios where you want to automate workflows involving group membership management, such as auditing group members, syncing group members with other systems, or triggering actions based on group membership changes.
Practical example:
You can use this node to retrieve all members of a GitLab group and then send notifications to those members or update an external database with the current group membership.
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. 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. |
| Return All | Whether to return all group members or limit the number of results returned. |
| Limit | Maximum number of group members to return if "Return All" is false. |
| Group ID | Numeric ID of the group whose members are to be listed. |
Output
- The output is a JSON array where each element represents a member of the specified GitLab group.
- Each member object contains detailed information about the user, such as username, name, access level, and other metadata as provided by the GitLab API.
- The node does not output binary data for this operation.
Dependencies
- Requires access to a GitLab instance, either the public GitLab server (
https://gitlab.com) or a self-hosted GitLab server. - Requires an API access token with sufficient permissions to read group membership.
- 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.
- No additional external dependencies beyond standard HTTP requests to GitLab API.
Troubleshooting
Invalid or missing Group ID:
The node requires a positive numeric Group ID. If the Group ID is missing or invalid, the node will throw an error. Ensure the Group ID is correct and exists in your GitLab instance.Authentication errors:
If the API token is invalid or lacks necessary permissions, the node will fail to fetch group members. Verify that the token has at least read access to groups.API rate limits or network issues:
If the GitLab API rate limits are exceeded or there are connectivity problems, the node may fail. Check network connectivity and consider handling rate limits by enabling pagination with "Return All" or limiting the number of results.JSON parsing errors:
Not applicable specifically for this operation, but ensure any optional JSON inputs (not relevant here) are correctly formatted.