Update Task Log
thehive.update_task_log
ActionBusiness appsconnection required
Calls the TheHive API with the connection's credentials.
Edit the text of a task log, or pin it to the case timeline.
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
3 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 |
|---|---|---|---|---|---|
log_id TheHive id of the task log entry. | string | Yes | — | — | ~41287768 |
message The replacement log text. | string | No | — | — | — |
include_in_timeline Epoch milliseconds at which to pin this entry to the case timeline. | number | No | — | ≥ 0 | — |
- At least one of message, include_in_timeline must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"log_id": "~41287768"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
log_id The task log 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": [],
"log_id": ""
}See Update Task Log 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.