Search Events
misp.search_events
ActionBusiness appsconnection required
Calls the MISP API with the connection's credentials.
Search events through restSearch, the endpoint MISP recommends.
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
8 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 |
|---|---|---|---|---|---|
value Match events holding an attribute with this value, e.g. an IP. | string | No | — | — | — |
type Restrict to events holding this attribute type, e.g. ip-dst. | string | No | — | — | — |
tags Comma-separated tag names the record must carry, e.g. tlp:amber,osint. | string | No | — | — | — |
date_from Earliest event date to include, as YYYY-MM-DD or a relative age like 30d. | string | No | — | — | 30d |
date_to Latest event date to include, as YYYY-MM-DD or a relative age like 1d. | string | No | — | — | — |
limit Maximum records to return in one page. Your MISP role may cap this lower. | number | No | — | 1–10000 | — |
page Which page of results to return, counting from 1. | number | No | — | ≥ 1 | — |
filters Any further restSearch filters as JSON; these win over the fields above. | object | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"date_from": "30d"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The matching records, unwrapped from their MISP envelope. | array | — |
count How many records this page returned. | number | — |
{
"count": 0,
"items": []
}See Search Events 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.