Update Attribute
misp.update_attribute
ActionBusiness appsconnection required
Calls the MISP API with the connection's credentials.
Merge a set of fields into an existing 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
2 fields, 2 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 |
|---|---|---|---|---|---|
attribute_id Numeric id or UUID of the MISP attribute. | string | Yes | — | — | 42 |
changes The attribute fields to change, as JSON; at least one is needed. | object | Yes | — | ≥ 1 characters | {"comment":"Confirmed malicious"} |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"attribute_id": "42",
"changes": {
"comment": "Confirmed malicious"
}
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id The attribute's numeric id. | string | — |
uuid The attribute's UUID. | string | — |
value The indicator as MISP stored it. | string | — |
{
"id": "",
"uuid": "",
"value": ""
}See Update 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.