# Elasticsearch - Workflow node | Docs - nodulz

Source: https://nodulz.com/docs/nodes/elasticsearch

Language: en

Search, count and manage Elasticsearch documents.

## Usage and specifics

Configure a compatible credential and service query or operation. Response shape depends on the service; inspect it before mapping. Account permissions apply to reads and writes.

Technical type : `elasticsearch`. Runtime : `nodulz`.

## Credentials and prerequisites

- [Elasticsearch](/docs/credentials) (`integration` / `elasticsearch`). Encoded Elasticsearch API key. Set the URL in the node.

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the [credentials guide](/docs/credentials) for access and rotation.

## Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

| Parameter | Type | Default | Values / limits |
| --- | --- | --- | --- |
| `credentialId` | `string` | `""` | - |
| `endpoint` | `string` | `"http://localhost:9200"` | - |
| `operation` | `enum` | `"search"` | `search`, `get`, `index`, `update`, `delete`, `count` |
| `index` | `string` | `""` | - |
| `documentId` | `string` | `""` | - |
| `body` | `string` | `"{}"` | - |
| `timeout` | `number` | `30` | -; ≥ 1, ≤ 600 |

## Configuration help

| Setting | Purpose and guidance |
| --- | --- |
| `operation`<br>Operation | Elasticsearch operation on one concrete index or alias. Indexing an existing ID replaces the document. |
| `timeout`<br>Timeout (seconds) | Between 1 and 600 seconds. Cancellation interrupts the running request. |

## Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

```json
{
  "credentialId": "",
  "endpoint": "http://localhost:9200",
  "operation": "search",
  "index": "",
  "documentId": "",
  "body": "{}",
  "timeout": 30
}
```

## Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.

See also : [Expressions and data](/docs/expressions), [Executions](/docs/executions), [Node catalog](/docs/nodes).

## Explore further

- [Features - nodulz](https://nodulz.com/product/overview)
- [Node catalog - nodulz](https://nodulz.com/product/catalog)
- [MCP server - nodulz](https://nodulz.com/product/mcp)
- [Pricing - nodulz](https://nodulz.com/pricing)
- [Use cases and workflow automation - nodulz](https://nodulz.com/use-cases)
- [Choose what your workflows can do. - nodulz](https://nodulz.com/compare)
- [Documentation - nodulz](https://nodulz.com/docs)