GitLab Extended icon

GitLab Extended

Extended GitLab node
Join our community

Actions66

Overview

This node operation fetches a specific note attached to a GitLab merge request. It is useful when you want to retrieve the content and metadata of a particular comment or discussion note made on a merge request in a GitLab project.

Common scenarios include:

  • Reviewing comments on a merge request programmatically.
  • Automating workflows that depend on notes or discussions in merge requests.
  • Extracting feedback or review comments for further processing or notifications.

For example, you might use this node to get a note by its ID from a merge request to analyze reviewer comments or to trigger other automation based on the note's content.

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. 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 to get the note. Must be a positive number.
Note ID The ID of the existing note to retrieve. Must be a positive number.

Output

The output is a JSON object representing the requested note on the merge request. This includes all standard fields returned by the GitLab API for a merge request note, such as:

  • id: The unique identifier of the note.
  • body: The text content of the note.
  • author: Information about the user who created the note.
  • created_at and updated_at: Timestamps for creation and last update.
  • Other metadata related to the note context within the merge request.

No binary data is output by this operation.

Dependencies

  • Requires access to a GitLab instance via its REST API.
  • Needs either saved credentials or custom authentication parameters including an API access token.
  • The node expects valid project identification either by numeric project ID or by owner and project name.
  • Proper permissions on the GitLab API token to read merge request notes are necessary.

Troubleshooting

  • Invalid or missing Note ID: Ensure the Note ID is a positive integer and corresponds to an existing note on the specified merge request.
  • Invalid Merge Request IID: The merge request IID must be positive and exist in the project.
  • Authentication errors: Verify that the API token has sufficient permissions to access merge request notes.
  • Project identification issues: If using custom authentication, ensure that either Project ID is set or both Project Owner and Project Name are correctly specified.
  • API rate limits or network errors: Check connectivity and GitLab API rate limits if requests fail unexpectedly.

Links and References

Discussion