Actions18
- Branch Actions
- File Actions
- Issue Actions
- Merge Request Actions
- Pipeline Actions
- Raw API Actions
Overview
This node integrates with GitLab to perform extended operations on various GitLab resources. Specifically, for the Issue - Get operation, it fetches detailed information about a single issue identified by its issue number within a specified GitLab project.
Typical use cases include:
- Retrieving the current status, description, and metadata of a specific issue in a GitLab project.
- Automating workflows that require issue details, such as syncing issue data with other tools or triggering actions based on issue state.
- Monitoring or reporting on individual issues programmatically.
Example: Fetching issue number 101 from a project to display its title, description, and status in an external dashboard.
Properties
| Name | Meaning |
|---|---|
| Issue Number | The numeric identifier of the issue to fetch, e.g., 101. This specifies which issue's details will be retrieved from GitLab. |
Output
The node outputs a JSON array where each element corresponds to the fetched issue's data structure as returned by the GitLab API. This includes fields such as issue ID, title, description, state (open/closed), author, assignees, labels, creation date, update date, and other metadata related to the issue.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with the GitLab API.
- Needs configuration of the target GitLab project either by project ID or by project owner and name.
- Uses internal helper functions to make authenticated HTTP requests to GitLab's REST API endpoints.
Troubleshooting
Common Issues:
- Incorrect or missing issue number parameter will cause failure to retrieve the issue.
- Invalid or insufficient API credentials can lead to authentication errors.
- If the project identification (ID or owner/name) is incorrect, the API call will fail.
Error Messages:
"Unknown resource: issue"— indicates the resource parameter was not set correctly.- HTTP 404 Not Found — likely means the issue number does not exist in the specified project.
- Authentication errors — check that the API key credential is valid and has appropriate permissions.
Resolutions:
- Verify the issue number is correct and exists in the project.
- Confirm API credentials are properly configured and have access rights.
- Ensure the project is correctly identified in the node credentials.