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 manage various GitLab resources programmatically. Specifically, the Issue - Get Many operation allows users to retrieve multiple issues from a GitLab project. This is useful for workflows that need to analyze, report on, or automate actions based on issue data.
Common scenarios include:
- Fetching all open issues in a project to generate reports.
- Retrieving a subset of issues filtered by criteria for further processing.
- Automating notifications or updates based on issue status changes.
For example, a user might configure this node to fetch all issues from a specific project and then use the output to create a dashboard summarizing issue statuses.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose between using saved credentials ("Credential") or specifying custom connection details ("Custom"). |
| GitLab Server | Base URL of the 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 available issues or limit the number of results. Defaults to false (limit applies). |
| Limit | Maximum number of issues to return when "Return All" is false. Default is 50. |
Output
The node outputs an array of JSON objects representing GitLab issues retrieved from the specified project. Each object corresponds to one issue and contains fields as returned by the GitLab API, such as:
- Issue ID and internal IID
- Title and description
- Labels
- State (open, closed)
- Author and assignee information
- Creation and update timestamps
This structured JSON output can be used downstream in n8n workflows for filtering, transformation, or integration with other systems.
The node does not output binary data for this operation.
Dependencies
- Requires access to a GitLab instance, either the public
https://gitlab.comor a self-hosted GitLab server. - Requires an API access token with appropriate permissions to read issues from the target project.
- Supports two authentication modes: using stored credentials or custom parameters entered directly in the node.
- No additional external dependencies beyond standard HTTP requests to GitLab's REST API.
Troubleshooting
- Invalid or missing project identification: If neither a valid project ID nor both project owner and name are provided (when using custom authentication), the request will fail. Ensure correct project identifiers are set.
- Insufficient permissions: The access token must have API scope permissions to read issues. Errors related to authorization indicate token scope or validity problems.
- Rate limiting: GitLab may throttle API requests if too many are made in a short time. Use the "Return All" option judiciously or implement delays.
- Malformed JSON in optional parameters: Although not applicable for this operation, other operations accept JSON input; invalid JSON will cause errors.
- Network or server errors: Check connectivity to the GitLab server URL and ensure it is reachable.
Common error messages:
- "Unknown resource" — indicates a misconfiguration of the resource parameter.
- "Project ID must be positive" — ensure numeric IDs are greater than zero.
- "Invalid JSON" — relevant for other operations accepting JSON input.