ActionGitLabUpdated September 2026

How do I add a comment to a GitLab issue or MR?

Short answer: You can add gitlab comment in GitLab by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GitLab Add GitLab Comment action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Add GitLab Comment in GitLab — start free All 10 GitLab actions

Add GitLab Comment in GitLab — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Project ID project_id	string	Required	Project ID. Example: 123
Issue IID issue_iid	string	Required	Issue IID. Example: 42
Comment Body body	string	Required	Comment Body. Example: Investigated — this is a duplicate of #38.

Sample request

{
  "project_id": "e.g. 123",
  "issue_iid": "e.g. 42",
  "body": "e.g. Investigated — this is a duplicate of #38."
}

Returns

{
  "id": 1001,
  "body": "Investigated — duplicate of #38.",
  "author": {
    "username": "johndoe"
  },
  "created_at": "2025-01-15T12:00:00Z"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Add GitLab Comment.

Any of these apps can fire this action as part of a workflow.

Google Sheets → GitLab

2 Google Sheets triggers

HubSpot → GitLab

18 HubSpot triggers

FAQ

Questions about Add GitLab Comment.

What does the Add GitLab Comment action do in GitLab?

Posts a comment on an issue, merge request, or commit. For AI-code-review bots or for cross-tool sync ("Linear status changed → comment on the linked MR").

What inputs does Add GitLab Comment require?

Required: Project ID, Issue IID, Comment Body. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if GitLab returns an error?

The run history shows the failed step with its input and the error message GitLab returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Add GitLab Comment support batch operations?

Run Add GitLab Comment inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within GitLab's rate limits.

More actions