Nexra
All connectors
Implemented
AI, documents, knowledge & search
Elasticsearch logo

Elasticsearch

Search, count, read and index documents in Elasticsearch on Elastic Cloud, with search_after and point-in-time paging.

Feed search and analytics indices from business systems and use search results in flows.

Build a flow with ElasticsearchProvider API documentation

Source actions

5

Destination actions

3

Data types

5

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

document count
  • Count documents
    Source

    Counts documents matching a Query DSL query (_count).

documents
  • Get document
    Source

    Reads one document by _id.

  • Search documents
    Source

    Runs a Query DSL search. Add a sort (with a unique tiebreaker) or a point in time for deep paging with search_after.

  • Update document fields
    Destination
    Duplicate protected

    Merges fields into an existing document by _id; optionally creates it when missing.

  • Index document
    Destination
    Duplicate protected

    Creates or replaces a document with an explicit _id.

indices
  • List indices
    Source

    Indices with health, document counts and size (_cat/indices).

mappings
  • Get index mapping
    Source

    Field mappings for an index, used to map document fields.

point in time
  • Open point in time
    Destination
    Not retried automatically

    Opens a point in time for consistent deep paging through Search documents. It expires after the keep-alive.

Authentication

Elasticsearch API key (encoded value)

Plans and access

Elastic Cloud Hosted deployments and Elastic Cloud Serverless projects. The API key's role descriptors limit indices and privileges (read, index, view_index_metadata, monitor).

Test environment

A 14-day Elastic Cloud trial can be used for testing.

Rate limits

No fixed request quota; the cluster rejects work with HTTP 429 when thread pools or circuit breakers are saturated.

Provider events

Elasticsearch does not deliver webhooks. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

  • Only Elastic Cloud Hosted (cloud.es.io, found.io, elastic-cloud.com) and Serverless (elastic.cloud) endpoints on port 443 are accepted. Self-managed clusters are not supported.
  • Bulk indexing, update-by-query, scripts, ES|QL, aggregations output and deletes are not exposed; aggregations in the query body are ignored in results.
  • Without a sort or point in time, paging uses from/size and stops at 10,000 hits.
  • Partial updates merge a document; scripted updates are not supported.