Bulk Update Cases
thehive.bulk_update_cases
ActionBusiness appsconnection required
Calls the TheHive API with the connection's credentials.
Apply the same field changes to several cases in one call.
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 |
|---|---|---|---|---|---|
case_ids Comma-separated case ids to change, or an array of ids. | string | Yes | — | — | ~4,~5 |
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.
{
"case_ids": "~4,~5",
"changes": {
"status": "InProgress"
}
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ids The case ids that were submitted. | array | — |
submitted How many ids were sent. | number | — |
accepted True when TheHive took the request. It answers 204, so this is not a count of the rows that actually changed. | boolean | — |
fields The names of the fields that were sent, sorted. | array | — |
{
"accepted": false,
"fields": [],
"ids": [],
"submitted": 0
}See Bulk Update Cases 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.