ActionJiraUpdated September 2026

How do I add a watcher to a Jira issue?

Short answer: You can add watcher in Jira by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Jira Add Watcher 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 Watcher in Jira — start free All 17 Jira actions

Add Watcher 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 issueKey	string	Required	Jira issue key in PROJECT-NUMBER format.
Account ID accountId	string	Required	Atlassian account ID for the user (a 24-char hex or longer cloud ID). Not the email or display name.

Sample request

{
  "issueKey": "e.g. PROJ-1",
  "accountId": "e.g. 5b10ac8d82e05b22cc7d4ef5"
}

Returns

{
  "success": true
}

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

Triggered by

Apps that pair well as the trigger for Add Watcher.

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 Watcher.

What does the Add Watcher action do in Jira?

Adds a user as a watcher on a Jira issue so they receive notifications on updates. Used to auto-loop in interested parties (PMs, designers, support).

What inputs does Add Watcher require?

Required: Issue Key, Account ID. 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 Watcher support batch operations?

Run Add Watcher 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