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 deletes a specific discussion note within a merge request on a GitLab instance. It is useful when you want to programmatically remove comments or notes that are part of discussions in merge requests, for example, to clean up outdated feedback or resolve irrelevant conversations automatically.
Practical scenarios include:
- Automating the cleanup of resolved or obsolete discussion notes after code review.
- Integrating with workflows that manage merge request discussions by removing notes based on certain triggers or conditions.
- Maintaining a tidy and relevant discussion history in merge requests by deleting unnecessary notes.
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 GitLab. 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. |
| Discussion ID | The ID of the discussion containing the note to delete, e.g., '123abc'. Required. |
| Note ID | The numeric ID of the note to delete within the discussion. Must be a positive integer. Required. |
Output
The output is a JSON array representing the result of the deletion operation. Typically, for a delete operation, the response may be empty or contain confirmation metadata from the GitLab API indicating successful deletion.
No binary data is output by this operation.
Dependencies
- Requires access to a GitLab instance via its REST API.
- Needs an API authentication token with sufficient permissions to delete discussion notes in merge requests.
- Supports either stored credentials configured in n8n or custom authentication parameters (server URL, access token, project identification).
- No additional external dependencies beyond standard HTTP requests to GitLab's API.
Troubleshooting
- Invalid or missing Discussion ID or Note ID: Ensure these IDs are correctly specified and correspond to existing discussion notes in the target merge request.
- Authentication errors: Verify that the access token has the necessary API scopes/permissions to delete discussion notes.
- Project identification issues: If using custom authentication, confirm that the project is correctly identified either by numeric ID or by owner and project name.
- API rate limits or network issues: Check connectivity to the GitLab server and ensure API rate limits have not been exceeded.
- Error messages from GitLab API: These typically indicate permission problems, invalid parameters, or non-existent resources. Review the error message details and adjust inputs accordingly.