Search Attributes

misp.search_attributes
ActionBusiness appsconnection required

Calls the MISP API with the connection's credentials.

Search attributes through restSearch — the indicator lookup.

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

9 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
value
The indicator to look for, e.g. an IP, a domain or a hash.
stringNo——8.8.8.8
type
Restrict to one MISP attribute type, e.g. ip-dst, domain or sha256.
stringNo———
category
Restrict to one MISP category, e.g. Network activity.
stringNo———
tags
Comma-separated tag names the record must carry, e.g. tlp:amber,osint.
stringNo———
date_from
Earliest event date to include, as YYYY-MM-DD or a relative age like 30d.
stringNo——30d
date_to
Latest event date to include, as YYYY-MM-DD or a relative age like 1d.
stringNo———
limit
Maximum records to return in one page. Your MISP role may cap this lower.
numberNo—1–10000—
page
Which page of results to return, counting from 1.
numberNo—≥ 1—
filters
Any further restSearch filters as JSON; these win over the fields above.
objectNo———

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "date_from": "30d",
  "value": "8.8.8.8"
}

Output

One shape.

result

FieldTypeExample
items
The matching records, unwrapped from their MISP envelope.
array—
count
How many records this page returned.
number—
{
  "count": 0,
  "items": []
}

See Search Attributes 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.