Disable Warninglists
misp.disable_warninglists
ActionBusiness appsconnection required
Calls the MISP API with the connection's credentials.
Switch off one or more warninglists, named by id or by name.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- MISP
- Secret shape
- the MISP automation key, or {"api_key": "…"}
- Config it needs
- base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, none 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 |
|---|---|---|---|---|---|
warninglist_ids Comma-separated warninglist ids to disable. | string | No | — | — | 1,2 |
names Comma-separated warninglist names; % is the wildcard. | string | No | — | — | — |
- At least one of warninglist_ids, names must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"warninglist_ids": "1,2"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
enabled The state the warninglists were moved to. | boolean | — |
saved True only when MISP reported the change as saved. | boolean | — |
message MISP's own wording, e.g. '2 warninglist(s) disabled'. | string | — |
errors MISP's error payload, or null when there was none. | any | — |
{
"enabled": false,
"errors": null,
"message": "",
"saved": false
}See Disable Warninglists run in a workflow.
In a technical demo we add the MISP connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.