Skip to content
For LLMsView as Markdown·

Elasticsearch

Index, search, and manage documents and clusters with the Elasticsearch API.

DetailValue
CategoryMonitoring
Base URLhttps://elasticsearch.example.com:9200
AuthenticationAPI Key
Endpoints8
Connector keyelastic

Using Elasticsearch in a workflow

  1. Go to Connections and click New Connection.
  2. Pick Elasticsearch from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

EndpointSummary
GET /_cluster/healthGet cluster health
GET /_cat/indicesList indices
PUT /{index}Create an index
DELETE /{index}Delete an index
GET /{index}/_doc/{id}Get a document
PUT /{index}/_doc/{id}Index a document
POST /{index}/_searchSearch documents
GET /{index}/_countCount documents

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /_cluster/health

Get cluster health

DetailValue
Operation IDmonitoring.getClusterHealth
MethodGET
Path/_cluster/health

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Elasticsearch connection from the Connection dropdown.
  3. In the Operation dropdown, select monitoring.getClusterHealth.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Elasticsearch API reference.

GET /_cat/indices

List indices

DetailValue
Operation IDmonitoring.listIndices
MethodGET
Path/_cat/indices

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Elasticsearch connection from the Connection dropdown.
  3. In the Operation dropdown, select monitoring.listIndices.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Elasticsearch API reference.

PUT /{index}

Create an index

DetailValue
Operation IDmonitoring.createIndex
MethodPUT
Path/{index}

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Elasticsearch connection from the Connection dropdown.
  3. In the Operation dropdown, select monitoring.createIndex.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Elasticsearch API reference.

DELETE /{index}

Delete an index

DetailValue
Operation IDmonitoring.deleteIndex
MethodDELETE
Path/{index}

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Elasticsearch connection from the Connection dropdown.
  3. In the Operation dropdown, select monitoring.deleteIndex.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Elasticsearch API reference.

GET /{index}/_doc/{id}

Get a document

DetailValue
Operation IDmonitoring.getDocument
MethodGET
Path/{index}/_doc/{id}

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Elasticsearch connection from the Connection dropdown.
  3. In the Operation dropdown, select monitoring.getDocument.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Elasticsearch API reference.

PUT /{index}/_doc/{id}

Index a document

DetailValue
Operation IDmonitoring.indexDocument
MethodPUT
Path/{index}/_doc/{id}

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Elasticsearch connection from the Connection dropdown.
  3. In the Operation dropdown, select monitoring.indexDocument.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Elasticsearch API reference.

POST /{index}/_search

Search documents

DetailValue
Operation IDmonitoring.searchDocumentsPost
MethodPOST
Path/{index}/_search

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Elasticsearch connection from the Connection dropdown.
  3. In the Operation dropdown, select monitoring.searchDocumentsPost.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Elasticsearch API reference.

GET /{index}/_count

Count documents

DetailValue
Operation IDmonitoring.countDocuments
MethodGET
Path/{index}/_count

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Elasticsearch connection from the Connection dropdown.
  3. In the Operation dropdown, select monitoring.countDocuments.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Elasticsearch API reference.