Create Attribute
misp.create_attribute
ActionBusiness appsconnection required
Calls the MISP API with the connection's credentials.
Add an indicator to an event as a new attribute.
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, 3 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 |
|---|---|---|---|---|---|
event_id Numeric id or UUID of the MISP event. | string | Yes | — | — | 1 |
type The MISP attribute type, e.g. ip-dst, domain, url, md5 or sha256. | string | Yes | — | — | ip-dst |
value The indicator itself, in the form the chosen type expects. | string | Yes | — | — | 8.8.8.8 |
category The MISP category; MISP picks the type's default when left blank. | string | No | — | — | Network activity |
to_ids Mark the indicator as suitable for automated detection. | boolean | No | true | — | — |
comment Free-text context stored alongside the indicator. | string | No | — | — | — |
distribution Who may see this attribute; 5 inherits the event's own level. | string | No | — | one of "0", "1", "2", "3", "4", "5" | — |
extra Any further MISP fields for this record, as a JSON object. | object | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"category": "Network activity",
"event_id": "1",
"to_ids": true,
"type": "ip-dst",
"value": "8.8.8.8"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id The new attribute's numeric id. | string | — |
uuid The new attribute's UUID. | string | — |
event_id The event it was added to. | string | — |
value The indicator as MISP stored it. | string | — |
{
"event_id": "",
"id": "",
"uuid": "",
"value": ""
}See Create Attribute 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.