Search Case Comments
elastic_security.find_comments
ActionBusiness appsconnection required
Calls the Elastic Security API with the connection's credentials.
Page through the comments and alerts attached to a case.
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
4 fields, 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 |
|---|---|---|---|---|---|
case_id Identifier of the case, as returned by Create Case or Search Cases. | string | Yes | — | — | 1b4f9a10-8c2e-11ee-9c3a-0242ac120002 |
sort_order Order the results are returned in. | string | No | desc | one of "desc", "asc" | — |
page Page of results to return, counting from 1. | number | No | 1 | 1–10000 | — |
per_page How many results to return per page. Kibana caps this at 100. | number | No | 20 | 1–100 | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"case_id": "1b4f9a10-8c2e-11ee-9c3a-0242ac120002",
"page": 1,
"per_page": 20,
"sort_order": "desc"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
comments The attachments on this page. | array | — |
count How many records this page actually returned. | number | — |
page The page number Kibana served. | number | — |
per_page The page size Kibana served. | number | — |
total How many records match the query in total. | number | — |
{
"comments": [],
"count": 0,
"page": 0,
"per_page": 0,
"total": 0
}See Search Case Comments 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.