List Watchers
jira.list_watchers
ActionBusiness appsconnection required
Calls the Jira Cloud REST API with the connection's email and API token.
List the users watching a Jira issue.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Username & password
- Providers
- Jira
- Secret shape
- {"email", "api_token"}
- Config it needs
- domain
- Resolved by
- config.connection_id, else node.connection_id
Configuration
1 field, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
issue_key Issue key or numeric id, e.g. PROJ-123. Supports {{ }}. | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
watchers[].accountId The watcher's Atlassian accountId. | string | — |
watchers[].displayName The watcher's display name. | string | — |
watchers[].active False for a deactivated account. | boolean | — |
count How many items this call returned. | number | — |
is_watching True when the connection's own account is one of the watchers. | boolean | — |
{
"count": 0,
"is_watching": false,
"watchers": [
{
"accountId": "",
"active": false,
"displayName": ""
}
]
}See List Watchers run in a workflow.
In a technical demo we add the Jira connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.