ActionJiraUpdated September 2026

How do I post a comment on a Jira issue?

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

Add Comment in Jira — start free All 17 Jira actions

Add Comment in Jira — 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
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.

Triggered by

Apps that pair well as the trigger for Add Comment.

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

2 Google Sheets triggers

HubSpot → Jira

18 HubSpot triggers

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 run history shows the failed step with its input and the error message Jira 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 Comment support batch operations?

Run Add 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 Jira's rate limits.

More actions