How does OCNORA authenticate with Elasticsearch?

With a stored API key credential, shaped an API key, or {"username", "password"}. A connection test can check it when you add it.

What can I automate with Elasticsearch?

2 typed operations, each with a reference page listing its config fields and the shapes it emits.

What if the Elasticsearch operation I need is not listed?

Where Elasticsearch has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.

Are there templates that use Elasticsearch?

Not yet. Start from a blank workflow, or describe the workflow to Build with AI.

How are Elasticsearch calls controlled?

Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

Elasticsearch

Databases & warehousesAPI keyConnection test available

Elasticsearch — search and index documents (cluster health test).

OCNORA ships 2 typed Elasticsearch operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.

Ask about Elasticsearch

Before you connect Elasticsearch

Authentication: API key
Credential: an API key, or {"username", "password"}
Connection test: Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.

What you can do with Elasticsearch

Operations, grouped by what they do to your data.

Read and search 1

Other operations 1

Index Document

A sample Elasticsearch workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Elasticsearch trigger is needed.
2
Searchelasticsearch.search
Run a Query DSL search against an Elasticsearch index.
3
Index Documentelasticsearch.index_document
Index (create or overwrite) a document in an Elasticsearch index.

An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.

Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.

Operations 2

Elasticsearch questions

How does OCNORA authenticate with Elasticsearch?: With a stored API key credential, shaped an API key, or {"username", "password"}. A connection test can check it when you add it.
What can I automate with Elasticsearch?: 2 typed operations, each with a reference page listing its config fields and the shapes it emits.
What if the Elasticsearch operation I need is not listed?: Where Elasticsearch has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
Are there templates that use Elasticsearch?: Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
How are Elasticsearch calls controlled?: Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

See your first Elasticsearch workflow run.

Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.

Book a technical demo Talk to sales