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 enables interaction with GitLab's Merge Request resource, specifically supporting the deletion of notes attached to merge requests. It is useful in scenarios where you want to programmatically manage comments or notes on merge requests, such as cleaning up outdated feedback or removing irrelevant discussions.
For example, if a team uses automated workflows to moderate merge request discussions, this node can delete specific notes by their ID, helping maintain clarity and relevance in code review conversations.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose between using saved credentials ("Credential") or specifying 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 for authentication. 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. |
| Merge Request IID | The internal ID (IID) of the merge request from which the note will be deleted. Must be a positive number. |
| Note ID | The ID of the existing note to delete. Must be a positive number. |
Output
The node outputs JSON data representing the result of the delete note operation. Typically, this will be an empty response or confirmation that the note was successfully deleted. The output is structured as an array of JSON objects corresponding to each input item processed.
No binary data is produced by this operation.
Dependencies
- Requires access to a GitLab instance, either via saved credentials or custom connection parameters.
- Needs an API access token with sufficient permissions to delete notes on merge requests.
- No additional external dependencies beyond standard HTTP API calls to GitLab.
Troubleshooting
- Invalid or missing credentials: Ensure that the API token has the necessary permissions to modify merge requests and delete notes.
- Incorrect Project identification: When using custom authentication, verify that the project is correctly identified either by numeric ID or by owner and name.
- Non-existent Merge Request IID or Note ID: If the specified merge request or note does not exist, the API will return an error. Double-check these IDs.
- Permission errors: The user associated with the access token must have rights to delete notes on the target merge request.
- API rate limits: Excessive requests may trigger rate limiting; consider adding delays or handling retries.
Common error messages include:
- "404 Not Found" — The merge request or note ID does not exist.
- "401 Unauthorized" — Invalid or insufficient authentication.
- "403 Forbidden" — Lack of permission to delete the note.
Resolving these typically involves verifying credentials, permissions, and input parameters.