Actions66
- Branch Actions
- File Actions
- Group Actions
- Issue Actions
- Merge Request Actions
- Pipeline Actions
- Project Actions
- Raw API Actions
- Release Actions
- Tag Actions
Overview
The node "GitLab Extended" provides extended integration with GitLab, allowing users to interact with various GitLab resources and operations. Specifically, the Merge Request - Get Discussion operation fetches a particular discussion thread from a merge request by its ID.
This operation is useful when you want to retrieve detailed conversation threads related to code changes in a merge request, such as comments, replies, and their metadata. It helps teams review discussions, track feedback, or automate workflows based on discussion content.
Practical example:
- Automatically fetching a specific discussion from a merge request to analyze reviewer comments and trigger notifications or further automation steps.
- Integrating with other tools to display or archive merge request discussions for audit or compliance purposes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose between using saved credentials ("Credential") or providing 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 to operate on. Must be a positive number. |
| Discussion ID | The unique identifier of the discussion to fetch, e.g., "123abc". |
Output
The output JSON contains the full data of the requested discussion thread within the specified merge request. This includes all comments, replies, authorship information, timestamps, and any metadata associated with the discussion.
The structure corresponds directly to GitLab's API response for a merge request discussion, typically including fields like:
id: Discussion IDnotes: Array of notes/comments in the discussionindividual_note: Boolean indicating if it's a single note or a threaded discussionresolvable: Whether the discussion can be resolvedresolved: Whether the discussion is currently resolved- Other metadata about the discussion context and participants
No binary data is output by this operation.
Dependencies
- Requires an active connection to a GitLab instance, either via saved credentials or custom parameters.
- Needs an API access token with sufficient permissions to read merge request discussions.
- No additional external dependencies beyond standard HTTP requests to the GitLab API.
Troubleshooting
- Invalid or missing Discussion ID: The node requires a valid discussion ID string. Ensure the ID is correct and exists in the target merge request.
- Insufficient permissions: The access token must have API scope permissions to read merge request discussions. If unauthorized errors occur, verify token scopes.
- Incorrect Project or Merge Request IID: The merge request IID must be valid and correspond to the project. Using an incorrect IID or project info will cause "not found" errors.
- Network or URL issues: When using custom server URLs, ensure the base URL is correct and accessible.
- API rate limits: Frequent calls may hit GitLab API rate limits; handle accordingly.