Check Values Against Warninglists
misp.check_warninglist_values
ActionBusiness appsconnection required
Calls the MISP API with the connection's credentials.
Test indicators against the enabled warninglists before acting on them.
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
1 field, 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 |
|---|---|---|---|---|---|
values Comma-separated values to test, e.g. 8.8.8.8,example.com. | string | Yes | — | — | 8.8.8.8,example.com |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"values": "8.8.8.8,example.com"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
matches Each matched value mapped to the lists that hit. | object | — |
checked How many values were sent. | number | — |
matched How many of them a warninglist knows. | number | — |
clean The values no warninglist matched. | array | — |
{
"checked": 0,
"clean": [],
"matched": 0,
"matches": {}
}See Check Values Against 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.