Actions18
- Branch Actions
- File Actions
- Issue Actions
- Merge Request Actions
- Pipeline Actions
- Raw API Actions
Overview
This node integrates with GitLab to manage issues, specifically allowing users to create new issues within a GitLab project. It is useful in scenarios where you want to automate issue tracking by programmatically opening issues based on events or workflows, such as reporting bugs, feature requests, or tasks directly from other systems.
For example, you could use this node to automatically create an issue titled "Fix login bug" with a detailed description outlining the steps to reproduce the problem whenever a monitoring system detects an authentication failure.
Properties
| Name | Meaning |
|---|---|
| Title | The title of the issue to be created, e.g., "Fix login bug". This is a required field. |
| Description | A detailed description of the issue, such as "Steps to reproduce the bug". Optional. |
Output
The node outputs JSON data representing the newly created issue as returned by the GitLab API. This typically includes fields like the issue ID, title, description, state, creation date, and other metadata related to the issue.
No binary data output is produced 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 specifying the project owner and name.
- Uses internal helper functions to make authenticated HTTP requests to GitLab's REST API endpoints.
Troubleshooting
Common Issues:
- Missing or invalid API credentials will cause authentication failures.
- Incorrect project identification (wrong project ID or owner/name) will result in errors locating the project.
- Required fields like "Title" must be provided; otherwise, the node will throw validation errors.
Error Messages:
"Unknown resource: issue": Indicates the resource parameter was not set correctly."The 'oldLine' parameter must be a non-negative number.": Not relevant for issue creation but may appear if parameters for other operations are misconfigured.- API errors from GitLab (e.g., permission denied, invalid parameters) will be passed through and should be resolved by checking permissions and input values.