Actions18
- Branch Actions
- File Actions
- Issue Actions
- Merge Request Actions
- Pipeline Actions
- Raw API Actions
Overview
This node interacts with GitLab's API to perform various actions related to merge requests. Specifically, the "Get" operation for the "Merge Request" resource retrieves detailed information about a single merge request identified by its IID (internal ID). This is useful when you want to fetch the current state, metadata, or details of a specific merge request in a GitLab project.
Common scenarios include:
- Automating workflows that need to check the status or details of a particular merge request.
- Integrating GitLab merge request data into other systems or dashboards.
- Triggering subsequent automation steps based on merge request properties.
Example: Fetching the merge request with IID 7 to review its title, description, author, and status before deciding whether to merge or trigger further CI/CD pipelines.
Properties
| Name | Meaning |
|---|---|
| Merge Request IID | The internal ID (IID) of the merge request to retrieve, e.g., 7. This uniquely identifies the merge request within the project. |
Output
The output JSON contains the full details of the requested merge request as returned by the GitLab API. This typically includes fields such as:
id: The global ID of the merge request.iid: The internal ID within the project.title: Title of the merge request.description: Detailed description text.state: Current state (e.g., opened, closed, merged).author: Information about the user who created the merge request.created_at,updated_at: Timestamps.- Other metadata like source/target branches, labels, assignees, approvals, etc.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with GitLab.
- The node expects configuration of the GitLab project either by project ID or by owner/name combination.
- Uses internal helper functions to make authenticated HTTP requests to GitLab's REST API.
Troubleshooting
- Invalid IID: If the provided merge request IID does not exist or is incorrect, the API will return an error indicating the merge request was not found. Verify the IID value.
- Authentication errors: Ensure the API key credential has sufficient permissions to read merge requests in the target project.
- Project identification issues: The node requires correct project identification via credentials; misconfiguration can cause "project not found" errors.
- Rate limits: GitLab API rate limits may cause temporary failures; handle retries accordingly.