Remove Watcher
jira.remove_watcher
ActionBusiness appsconnection required
Calls the Jira Cloud REST API with the connection's email and API token.
Remove a user from a Jira issue's watchers.
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
2 fields, 2 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 | — | — | — |
account_id The user's Atlassian accountId — find it with jira.search_users. | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok True when Jira accepted the call. | boolean | — |
key The issue key the call acted on. | string | PROJ-123 |
account_id The accountId that was removed. | string | — |
{
"account_id": "",
"key": "PROJ-123",
"ok": false
}See Remove Watcher 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.