Update Issue
sentry.update_issue
ActionBusiness appsconnection required
Calls the Sentry API PUT /issues/{id}/.
Change a Sentry issue's status (resolve, unresolve or ignore).
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Sentry
- Secret shape
- the Sentry auth token
- Config it needs
- base_url, org
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 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_id Issue id. Supports {{ }}. | string | Yes | — | — | — |
status New status — Sentry accepts only the listed values. | string | No | resolved | one of "resolved", "unresolved", "ignored" | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"status": "resolved"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
id | string | — |
status | string | — |
{
"id": "",
"ok": false,
"status": ""
}Related Sentry nodes
See Update Issue run in a workflow.
In a technical demo we add the Sentry connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.