Add Comment: Jira 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
Issue Key or ID issue_key	string	Required	Issue Key or ID. Example: PROJ-123
Comment body	string	Required	The comment text

Sample request

{
  "issue_key": "e.g. PROJ-123",
  "body": "e.g. Investigated this — root cause is in the auth middleware."
}

Returns

{
  "id": "10001",
  "body": {
    "content": [
      {
        "content": [
          {
            "text": "Comment text"
          }
        ]
      }
    ]
  },
  "author": {
    "displayName": "John Doe"
  },
  "created": "2025-01-15T12:00:00.000+0000"
}

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

FAQ

Questions about Add Comment.

What does the Add Comment action do in Jira?

Adds a comment to an existing Jira issue with optional visibility restriction (role or group). Used for automation activity logs, AI summary notes, or external system pings.

What inputs does Add Comment require?

Required: Issue Key or ID, Comment. 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 Jira 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 Comment support batch operations?

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

More actions