- Integrations
- /
- Jira
- /
- Actions
- /
- Add Watcher
ActionJiraUpdated May 2026
How do I add a watcher to a Jira issue?
Short answer: Drop the "Jira → Add Watcher" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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.
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 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 Watcher support batch operations?
Yes. Run Add Watcher 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
Other Jira actions.
Action
Add Comment
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.
ActionAssign Issue
Assigns a Jira issue to a user (by accountId) or unassigns it. The standard routing action for AI-driven triage or rotating on-call assignment.
ActionCreate Issue
Creates a new issue (story, task, bug, epic, etc.) in a Jira project with summary, description, type, assignee, priority, labels, components, and custom fields. Standard write for converting external alerts into tracked work.
ActionDelete Issue
Permanently deletes a Jira issue by key or ID. Irreversible; pass deleteSubtasks=true to also remove children. Most teams transition to a Cancelled status instead.
ActionGet Issue
Retrieves a Jira issue by its key (ABC-123) or numeric ID with summary, description, status, assignee, comments, and custom fields. The standard read after a trigger fires with an ID.
ActionGet Project
Returns details of a Jira project: name, key, lead, issue types, components, and versions. Used to enrich a trigger or validate a project reference.
Send add watcher from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.