Actions11
Overview
This node extends GitLab API functionality by allowing users to interact with various GitLab resources such as branches, files, issues, pipelines, and raw API endpoints. Specifically, for the Issue - Create operation, it enables creating a new issue in a specified GitLab project.
Typical use cases include automating issue creation based on external triggers or workflows, such as when a bug report is submitted via a form or when an error occurs in another system. For example, you could automatically create a GitLab issue with a title and description whenever a monitoring alert fires.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with GitLab: either using an Access Token or OAuth2 credentials. |
| Project Owner | The username or group name that owns the GitLab project where the issue will be created. |
| Project Name | The repository name within the owner’s namespace where the issue will be created. |
| Title | The title of the new issue to be created. |
| Description | (Optional) A detailed description of the issue. |
Output
The node outputs JSON data representing the newly created issue as returned by the GitLab API. This includes all standard issue fields such as issue ID, title, description, state, author information, timestamps, and other metadata provided by GitLab.
No binary data output is produced by this operation.
Dependencies
- Requires a valid GitLab API authentication credential, either an access token or OAuth2 token.
- The node depends on internal helper functions to make HTTP requests to GitLab's REST API.
- No additional external services are required beyond GitLab itself.
Troubleshooting
Common Issues:
- Invalid or missing authentication credentials will cause authorization errors.
- Incorrect project owner or repository names may result in "project not found" errors.
- Missing required parameters like title will cause validation errors from the API.
Error Messages:
"Unknown resource: issue": Indicates the resource parameter was set incorrectly; ensure "issue" is selected.- API errors related to permissions or invalid input will be passed through; verify your token scopes and input values.
Resolution Tips:
- Double-check the spelling and casing of the project owner and repository.
- Ensure the authentication method matches the configured credentials.
- Provide all required fields, especially the issue title.