Update Task
thehive.update_task
ActionBusiness appsconnection required
Calls the TheHive API with the connection's credentials.
Merge fields into a task, such as its status or assignee.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- TheHive
- Secret shape
- the TheHive API key, or {"api_key": "…"}
- Config it needs
- base_url
- 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 |
|---|---|---|---|---|---|
task_id TheHive id of the task. | string | Yes | — | — | ~41156696 |
changes The fields to merge into the record, as a JSON object using TheHive's own field names, e.g. {"status": "InProgress", "assignee": "analyst"}. | object | Yes | — | ≥ 1 characters | {"status":"InProgress"} |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"changes": {
"status": "InProgress"
},
"task_id": "~41156696"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
task_id The task that was changed. | string | — |
accepted True when TheHive took the change. It answers 204 with no body, so the updated record is not returned — read it back if you need it. | boolean | — |
fields The names of the fields that were sent, sorted. | array | — |
{
"accepted": false,
"fields": [],
"task_id": ""
}See Update Task run in a workflow.
In a technical demo we add the TheHive connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.