Follow Or Unfollow Alert
thehive.follow_alert
ActionBusiness appsconnection required
Calls the TheHive API with the connection's credentials.
Start or stop following an alert, which controls source updates.
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, 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 |
|---|---|---|---|---|---|
alert_id TheHive id of the alert. | string | Yes | — | — | ~41353304 |
follow True to follow the alert, false to unfollow it. | boolean | No | true | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"alert_id": "~41353304",
"follow": true
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
alert_id The alert that was changed. | string | — |
follow The follow state that was requested. | boolean | — |
accepted True when TheHive took the request; it answers with no body. | boolean | — |
{
"accepted": false,
"alert_id": "",
"follow": false
}See Follow Or Unfollow Alert 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.