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 fetches discussions from a specific merge request in a GitLab project. Discussions are threads of comments and notes related to the merge request, useful for code review conversations, feedback, and collaboration.
Typical use cases include:
- Retrieving all discussion threads on a merge request to analyze or display comments.
- Automating workflows that respond to comments or discussion activity on merge requests.
- Integrating GitLab merge request discussions into external tools like chat apps or issue trackers.
For example, you might use this node to get all discussions on a merge request to generate a summary report of reviewer comments or to trigger notifications when new discussions appear.
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. |
| Return All | Whether to return all discussion results or limit the number returned. Defaults to false (limit applies). |
| Limit | Maximum number of discussion results to return if "Return All" is false. Default is 50. |
| Merge Request IID | The internal ID (IID) of the merge request to fetch discussions from. Must be a positive number. |
Output
The output is an array of JSON objects representing the discussions retrieved from the specified merge request. Each discussion object typically contains:
- Discussion ID
- Notes/comments within the discussion
- Author information
- Timestamps
- Resolved/unresolved status
- Position information related to code diffs (if applicable)
This data structure allows downstream nodes or workflows to process individual discussion threads and their content.
The node does not output binary data for this operation.
Dependencies
- Requires access to a GitLab instance via its REST API.
- Needs either saved credentials or custom authentication details including a personal access token with appropriate API permissions.
- No additional external dependencies beyond standard HTTP requests to GitLab's API.
Troubleshooting
- Invalid or missing Merge Request IID: Ensure the IID is a positive integer and corresponds to an existing merge request in the project.
- Authentication errors: Verify that the personal access token or saved credentials have sufficient permissions to read merge request discussions.
- Project identification issues: When using custom authentication, ensure that either the numeric Project ID is provided or both Project Owner and Project Name are correctly set.
- API rate limits or network errors: Check connectivity to the GitLab server and consider handling rate limits if many requests are made.
- Invalid JSON in parameters: Although not typical for this operation, other operations may require valid JSON; ensure inputs are well-formed.
If the node throws errors about unknown resources or operations, confirm that the Resource is set to "Merge Request" and Operation to "Get Discussions".