Update Case

elastic_security.update_case
ActionBusiness appsconnection required

Calls the Elastic Security API with the connection's credentials.

Change a case's status, severity, assignees or text. The version from the last read is required, so a concurrent edit is rejected rather than lost.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Elastic Security
Secret shape
the Kibana API key ("ApiKey <encoded>" or the bare encoded value), or {"api_key": "…"}
Config it needs
kibana_url, space_id, owner
Resolved by
config.connection_id, else node.connection_id

Configuration

11 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
case_id
Identifier of the case, as returned by Create Case or Search Cases.
stringYes——1b4f9a10-8c2e-11ee-9c3a-0242ac120002
version
The case's current version token, from Get Case or Search Cases.
stringYes———
status
New lifecycle state for the case.
stringNo—one of "open", "in-progress", "closed"—
severity
New severity for the case.
stringNo—one of "low", "medium", "high", "critical"—
title
New title for the case, up to 160 characters.
stringNo—≤ 160 characters—
description
New Markdown description, up to 30000 characters.
stringNo—≤ 30000 characters—
tags
Replacement tag list for the case.
arrayNo—array of string—
category
New category for the case, up to 50 characters.
stringNo—≤ 50 characters—
assignees
Replacement assignee list of user profile uids, at most 10.
arrayNo—≤ 10 characters; array of string—
connector
Replacement connector for the case as {id, name, type, fields}.
objectNo———
custom_fields
Replacement custom field values as {key, type, value} objects.
arrayNo—array of object—
  • At least one of status, severity, title, description, tags, category, assignees, connector, custom_fields must be set.

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "case_id": "1b4f9a10-8c2e-11ee-9c3a-0242ac120002"
}

Output

One shape.

result

FieldTypeExample
cases
Every case Elastic returned for the update.
array—
count
How many cases came back.
number—
case
The first updated case, or null when none came back.
object—
{
  "case": {},
  "cases": [],
  "count": 0
}

Notes

  • Elastic's update route is a bulk one and answers with an array; the node reports that array and its count rather than implying a single result.

See Update Case run in a workflow.

In a technical demo we add the Elastic Security connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.