gitlab api proInstall

Summary

Update a specific note within a merge request discussion, modifying its text or resolution status.

Inputs

• Authentication — Choose whether to use saved credentials or provide custom GitLab server URL and access token.
• GitLab Server — Base URL of your GitLab instance, used if Custom authentication is selected.
• Access Token — Personal access token with API permissions, used if Custom authentication is selected.
• Project Locator — Choose how to identify the project: by numeric ID or by owner and name (path).
• Project ID — Numeric project ID when 'ID' is chosen as Project Locator.
• Project Owner — Namespace or owner of the project when 'Path' is chosen as Project Locator.
• Project Name — Project slug or name when 'Path' is chosen as Project Locator.
• Merge Request IID (required) — Internal ID (IID) of the merge request to update the discussion note in (positive number).
• Discussion ID (required) — ID of the discussion containing the note to update.
• Note ID (required) — ID of the existing note to update (positive number).
• Body — New text content for the note; omit or leave empty if changing resolved state instead.
• Resolved — Set the resolution status of the discussion note: resolve, unresolve, or do not change (default).

Output shape

a single record representing the updated discussion note

The operation either updates the note's body text or its resolved state; these two cannot be changed simultaneously. The response contains the updated note object from GitLab.

Examples

Example 1: Update the text body of a discussion note

Provide the merge request IID, discussion ID, note ID, and the new body text, leaving 'Resolved' as 'Do Not Change'.

Example 2: Change the resolved state of a discussion note

Provide the merge request IID, discussion ID, note ID, and set 'Resolved' to 'Resolve' or 'Unresolve', leaving the body empty.

Links

• n8n community nodes installation guide