Unpublish Event
misp.unpublish_event
ActionBusiness appsconnection required
Calls the MISP API with the connection's credentials.
Take a published event back off the wire.
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 |
|---|---|---|---|---|---|
event_id Numeric id or UUID of the MISP event. | string | Yes | — | — | 1 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"event_id": "1"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
event_id The event that was targeted. | string | — |
saved True only when MISP reported the change as saved. | boolean | — |
message MISP's own wording for the outcome. | string | — |
errors MISP's error payload, or null when there was none. | any | — |
{
"errors": null,
"event_id": "",
"message": "",
"saved": false
}See Unpublish Event 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.