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 interacts with GitLab's API to manage issues within a specified project. The "Get" operation for the "Issue" resource fetches details of a single issue by its internal ID (IID) from a GitLab project.
Typical use cases include:
- Retrieving detailed information about a specific issue in a project for reporting or automation.
- Integrating issue data into workflows, such as triggering actions based on issue status or content.
- Synchronizing issue details with other tools or databases.
For example, you might use this node to fetch an issue by its number to check its current state or description before deciding whether to update it or notify a team.
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. |
| Issue IID | The internal ID (number) of the issue to fetch. Must be a positive integer. This is required. |
Output
The node outputs the JSON representation of the requested issue as returned by the GitLab API. This includes all standard fields describing the issue, such as:
- Issue title
- Description
- State (open, closed)
- Labels
- Author and assignees
- Creation and update timestamps
- Other metadata related to the issue
The output is structured as an array of JSON objects, each corresponding to one input item processed. Since this operation fetches a single issue per execution, the array will typically contain one object per input item.
No binary data is produced by this operation.
Dependencies
- Requires access to a GitLab instance, either the public
https://gitlab.comor a self-hosted server. - Requires an API access token with appropriate permissions to read project issues.
- If using saved credentials, the node expects a configured credential containing the necessary authentication.
- If using custom authentication, the user must provide the GitLab server URL, access token, and project identification details.
Troubleshooting
- Invalid or missing Issue IID: The node requires a positive integer for the issue IID. Providing zero, negative, or non-numeric values will cause errors.
- Authentication errors: If the access token is invalid or lacks permissions, the API request will fail. Ensure the token has at least read access to the project’s issues.
- Project identification issues: When using custom authentication, if neither a valid project ID nor both project owner and name are provided, the node may not locate the project correctly.
- API rate limits or network issues: Standard GitLab API limitations apply; ensure network connectivity and respect rate limits.
- Error messages typically indicate the nature of the problem, such as "Unauthorized" for auth failures or "Not Found" if the issue or project does not exist.