Publish Event
misp.publish_event
ActionBusiness appsconnection required
Calls the MISP API with the connection's credentials.
Publish an event, which MISP usually runs as a background job.
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 | — |
job_id The background job id, when MISP queued one. | string | — |
queued True when publishing was handed to a worker. | boolean | — |
saved True when MISP published it in the request itself. | boolean | — |
message MISP's own wording for the outcome. | string | — |
{
"event_id": "",
"job_id": "",
"message": "",
"queued": false,
"saved": false
}Notes
- A queued publish has not happened yet: poll the event with misp.get_event if a later step depends on it being published.
See Publish 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.