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 provides extended integration with GitLab, allowing users to perform various actions on GitLab resources such as branches, pipelines, tags, releases, groups, projects, issues, merge requests, files, and raw API calls. Specifically for the Merge Request resource with the Reopen operation, the node reopens a previously closed merge request in a specified GitLab project.
This functionality is useful in scenarios where a merge request was closed prematurely or needs to be revisited after further changes or discussions. For example, a developer might want to reopen a merge request to continue work or address review comments without creating a new one.
Properties
| Name | Meaning |
|---|---|
| Authentication | Select whether to use saved credentials ("Credential") or provide custom connection details ("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. |
Additional properties relevant to the Merge Request - Reopen operation (inherited from the general merge request parameters) include:
| Name | Meaning |
|---|---|
| Merge Request IID | The internal ID number of the merge request to reopen (must be positive). |
Output
The node outputs JSON data representing the updated merge request after reopening it. This typically includes fields such as the merge request's ID, title, description, state (which will be "opened" after reopening), author, timestamps, and other metadata returned by the GitLab API.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to a GitLab instance, either via saved credentials or custom authentication.
- Needs an API access token with sufficient permissions to modify merge requests in the target project.
- The node uses GitLab's REST API endpoints to perform operations.
- No additional external services are required beyond GitLab itself.
Troubleshooting
- Invalid or missing project identification: If neither a valid project ID nor both project owner and project name are provided (when using custom authentication), the node may fail to locate the project. Ensure these fields are correctly set.
- Insufficient permissions: The access token must have API rights to update merge requests. Errors related to authorization indicate that the token lacks necessary scopes.
- Invalid merge request IID: Providing a non-positive or incorrect merge request IID will cause errors. Verify the IID corresponds to an existing merge request.
- Network or server errors: Connectivity issues or incorrect GitLab server URLs can cause failures. Confirm the server URL and network accessibility.
- Error messages: The node throws errors if required parameters are missing or invalid, or if the GitLab API returns an error. Review the error message details to identify the cause.