Actions11
Overview
This node interacts with GitLab to perform various operations on different resources such as branches, files, issues, pipelines, and raw API requests. Specifically for the Issue - Get operation, it retrieves detailed information about a single issue from a specified GitLab project.
Typical use cases include:
- Fetching details of a specific issue by its number to monitor progress or extract metadata.
- Integrating GitLab issue data into workflows for reporting, notifications, or automation.
- Using issue information to trigger downstream processes based on issue status or content.
For example, you might use this node to get the current state and description of an issue in a project to send a summary email or update a dashboard.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate with GitLab: either "Access Token" or "OAuth2". |
| Project Owner | The username or group name that owns the GitLab project (URL-encoded internally). |
| Project Name | The repository/project name within the owner’s namespace. |
| Issue Number | The unique numeric identifier of the issue to retrieve within the specified project. |
Output
The output is a JSON array where each item corresponds to the retrieved issue's data structure as returned by the GitLab API. This includes fields such as issue ID, title, description, state, author, assignees, labels, creation date, update date, and other metadata related to the issue.
No binary data is output by this operation.
Dependencies
- Requires a valid GitLab API authentication credential, either an access token or OAuth2 token.
- The node uses internal helper functions to make HTTP requests to GitLab’s REST API endpoints.
- No additional external dependencies beyond standard n8n credentials and HTTP request capabilities.
Troubleshooting
Common Issues:
- Incorrect project owner or repository name can lead to "404 Not Found" errors.
- Providing an invalid or expired authentication token will cause authorization failures.
- Specifying an issue number that does not exist in the project will result in an error response from GitLab.
Error Messages:
"Unknown resource: issue": Occurs if the resource parameter is incorrectly set; ensure "issue" is selected.- HTTP 401 Unauthorized: Check that the authentication token is valid and has sufficient permissions.
- HTTP 404 Not Found: Verify the project owner, repository name, and issue number are correct.
Resolution Tips:
- Double-check spelling and case sensitivity of project owner and repository.
- Confirm the issue number exists in the target project.
- Refresh or regenerate API tokens if authentication errors persist.