Actions18
- Branch Actions
- File Actions
- Issue Actions
- Merge Request Actions
- Pipeline Actions
- Raw API Actions
Overview
This node extends GitLab API functionality by allowing users to interact with various GitLab resources, including merge requests. Specifically, the "Create Note" operation under the Merge Request resource enables adding a comment (note) to an existing merge request identified by its IID (internal ID). This is useful for code review workflows where team members want to leave feedback or remarks directly on a merge request.
Common scenarios:
- Adding review comments or general notes to a merge request.
- Automating notifications or reminders by programmatically posting notes.
- Integrating GitLab merge request discussions into broader automation workflows.
Example:
You have a CI/CD pipeline that runs tests and wants to automatically post a note on a merge request indicating test results or status updates.
Properties
| Name | Meaning |
|---|---|
| Merge Request IID | The internal ID of the merge request to which the note will be added, e.g., 7. |
| Note Body | The text content of the note to add, e.g., "Looks good to me" or any other comment. |
Output
The node outputs JSON data representing the newly created note object returned from the GitLab API. This typically includes details such as:
- Note ID
- Author information
- Creation timestamp
- Note body text
- Associated merge request IID
If multiple input items are processed, the output is an array of such note objects, each corresponding to one input item.
The node does not output binary data for this operation.
Dependencies
- Requires an API key credential for authenticating with GitLab.
- Needs configuration of project identification either by numeric project ID or by owner/name combination.
- Uses GitLab's REST API endpoints related to merge requests and notes.
Troubleshooting
- Invalid Merge Request IID: If the IID does not correspond to an existing merge request, the API will return an error. Verify the IID is correct and the authenticated user has access.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions to post notes on merge requests.
- Empty Note Body: The note body is required; submitting an empty string may cause the API to reject the request.
- API Rate Limits: Frequent automated calls might hit GitLab rate limits; consider adding delays or handling rate limit responses gracefully.