Appearance
Elasticsearch
Index, search, and manage documents and clusters with the Elasticsearch API.
| Detail | Value |
|---|---|
| Category | Monitoring |
| Base URL | https://elasticsearch.example.com:9200 |
| Authentication | API Key |
| Endpoints | 8 |
| Connector key | elastic |
Using Elasticsearch in a workflow
- Go to Connections and click New Connection.
- Pick Elasticsearch from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /_cluster/health | Get cluster health |
GET /_cat/indices | List 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}/_search | Search documents |
GET /{index}/_count | Count documents |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /_cluster/health
Get cluster health
| Detail | Value |
|---|---|
| Operation ID | monitoring.getClusterHealth |
| Method | GET |
| Path | /_cluster/health |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Elasticsearch connection from the Connection dropdown.
- In the Operation dropdown, select
monitoring.getClusterHealth. - 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
| Detail | Value |
|---|---|
| Operation ID | monitoring.listIndices |
| Method | GET |
| Path | /_cat/indices |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Elasticsearch connection from the Connection dropdown.
- In the Operation dropdown, select
monitoring.listIndices. - 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
| Detail | Value |
|---|---|
| Operation ID | monitoring.createIndex |
| Method | PUT |
| Path | /{index} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Elasticsearch connection from the Connection dropdown.
- In the Operation dropdown, select
monitoring.createIndex. - 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
| Detail | Value |
|---|---|
| Operation ID | monitoring.deleteIndex |
| Method | DELETE |
| Path | /{index} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Elasticsearch connection from the Connection dropdown.
- In the Operation dropdown, select
monitoring.deleteIndex. - 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
| Detail | Value |
|---|---|
| Operation ID | monitoring.getDocument |
| Method | GET |
| Path | /{index}/_doc/{id} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Elasticsearch connection from the Connection dropdown.
- In the Operation dropdown, select
monitoring.getDocument. - 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
| Detail | Value |
|---|---|
| Operation ID | monitoring.indexDocument |
| Method | PUT |
| Path | /{index}/_doc/{id} |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Elasticsearch connection from the Connection dropdown.
- In the Operation dropdown, select
monitoring.indexDocument. - 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
| Detail | Value |
|---|---|
| Operation ID | monitoring.searchDocumentsPost |
| Method | POST |
| Path | /{index}/_search |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Elasticsearch connection from the Connection dropdown.
- In the Operation dropdown, select
monitoring.searchDocumentsPost. - 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
| Detail | Value |
|---|---|
| Operation ID | monitoring.countDocuments |
| Method | GET |
| Path | /{index}/_count |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Elasticsearch connection from the Connection dropdown.
- In the Operation dropdown, select
monitoring.countDocuments. - 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.