Add Task Log
thehive.create_task_log
ActionBusiness appsconnection required
Calls the TheHive API with the connection's credentials.
Write a log entry on a task, which is how analysts record work.
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
4 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 |
message The log text, as Markdown. | string | Yes | — | — | — |
start_date When the logged work happened, in epoch milliseconds. | number | No | — | ≥ 0 | — |
include_in_timeline Epoch milliseconds at which to pin this entry to the case timeline. | number | No | — | ≥ 0 | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"task_id": "~41156696"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
_id TheHive's internal id for the task log. | string | — |
message The log text, as Markdown. | string | — |
date When the log entry happened, in epoch milliseconds. | number | — |
owner Login of the user the log belongs to. | string | — |
includeInTimeline Set when the entry is pinned to the case timeline. | number | — |
_createdAt When the log was written, in epoch milliseconds. | number | — |
{
"_createdAt": 0,
"_id": "",
"date": 0,
"includeInTimeline": 0,
"message": "",
"owner": ""
}See Add 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.