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 operation updates an existing issue in a GitLab project. It allows users to modify the issue's title, description, labels, and state (open or closed). This is useful for automating issue management workflows, such as updating bug reports, feature requests, or task statuses directly from n8n without manually accessing the GitLab interface.
Practical examples:
- Automatically update issue details when a related event occurs in another system (e.g., customer support ticket updated).
- Change the state of an issue to "closed" after a successful deployment.
- Add or modify labels on issues based on external triggers or conditions.
Properties
| Name | Meaning |
|---|---|
| Authentication | Select whether to use saved credentials ("Credential") or provide custom fields ("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. 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. |
| Title | The new title text for the issue, e.g., "Fix login bug". Required. |
| Description | Detailed description of the issue, e.g., "Steps to reproduce the bug". Optional. |
| Issue IID | The internal issue number (must be positive) identifying which issue to update. Required. |
| Labels | Comma-separated label names to apply to the issue. Optional. |
| State | Desired issue state. Options: - Open ( reopen) - Close ( close) Default is Open. |
Output
The node outputs an array of JSON objects representing the updated issue(s) returned by the GitLab API. Each object contains detailed information about the issue, including its updated title, description, labels, state, and other metadata as provided by GitLab.
No binary data output is produced by this operation.
Dependencies
- Requires access to a GitLab instance via API.
- Requires either:
- Saved credentials configured in n8n with appropriate API access rights, or
- Custom authentication parameters including GitLab server URL and a personal access token with sufficient permissions.
- The personal access token must have API permissions to update issues in the target project.
Troubleshooting
- Invalid or missing Issue IID: The node requires a positive integer for the issue identifier. Ensure the "Issue IID" property is set correctly.
- Authentication errors: If using custom authentication, verify that the GitLab server URL and access token are correct and have necessary permissions.
- Project identification issues: When using custom authentication, ensure that either the numeric Project ID is provided or both Project Owner and Project Name are specified correctly.
- API errors: Errors from GitLab API (e.g., permission denied, issue not found) will be thrown by the node. Check the error message for details and verify project and issue identifiers.
- Invalid JSON in labels or description: Labels should be comma-separated strings; descriptions should be plain text. Avoid malformed inputs.