Update Feed
misp.update_feed
ActionBusiness appsconnection required
Calls the MISP API with the connection's credentials.
Merge a set of fields into an existing feed configuration.
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 |
|---|---|---|---|---|---|
feed_id Numeric id or UUID of the feed. | string | Yes | — | — | 1 |
changes The feed fields to change, as JSON; at least one is needed. | object | Yes | — | ≥ 1 characters | {"enabled":true} |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"changes": {
"enabled": true
},
"feed_id": "1"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
id The feed's numeric id. | string | — |
name The feed's name. | string | — |
{
"id": "",
"name": ""
}See Update Feed 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.