Add GitLab Comment: GitLab action

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.

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Add GitLab Comment support batch operations?

Yes. Run Add GitLab Comment inside a Loop node to process arrays. Tiny Command handles GitLab's rate limits automatically so you don't have to throttle manually.

More actions