Elasticsearch is a distributed, RESTful search and analytics engine capable of addressing a growing number of use cases. It provides real-time search and analytics for all types of data.
Elasticsearch is a distributed, RESTful search and analytics engine capable of addressing a growing number of use cases. It provides real-time search and analytics for all types of data. On Nagent, Elasticsearch is exposed as a fully-configurable databases integration that any agent can call — 4 actions, and API_KEY, BASIC authentication. No code is required to wire Elasticsearch into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Elasticsearch to automate the kinds of tasks databases teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Elasticsearch into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Elasticsearch, with input parameters and output schema. Drop these into any step of an agent built in Helix.
ELASTICSEARCH_GET_INDEX_SCHEMATool to get the complete schema/mapping of a specific Elasticsearch index. Use when you need to understand the structure, field types, and mappings of an index.
Input parameters
The name of the index to get schema information for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ELASTICSEARCH_LIST_INDICESTool to list all available Elasticsearch indices. Use when you need to get a list of indices in your Elasticsearch cluster, optionally filtering by pattern, health status, or other criteria.
Input parameters
A comma-separated string of index names or wildcard expressions to limit the returned information. For example, 'my-index-*,another-index'. If not provided, information for all indices is returned.
The health status to filter indices by (green, yellow, or red).
A comma-separated string of column names to sort by. For example, 'index,health'.
Type of index that wildcard patterns can match. Supports comma-separated values, e.g., 'open,hidden'. 'all' matches all indices by default.
If true, only shows information about primary shards.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ELASTICSEARCH_PING_CLUSTERTool to ping the Elasticsearch cluster and check if it is running. Use when you need to verify cluster connectivity and health status before performing operations.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ELASTICSEARCH_QUERY_INDEXTool to query an Elasticsearch index with various filters, time ranges, and pagination support. Use when you need to search for documents in an index with complex filtering criteria.
Input parameters
Starting offset for pagination (default: 0)
Number of results to return (default: 10, max: 1000 to prevent context overload)
Sort order for results
Free text search query (uses query_string query)
Specific fields to return (if not specified, returns all fields)
Enable highlighting for search terms
The name of the index to query. Must be a non-empty string.
Time-based filter for timestamp fields
Exact term filters for specific field values
Range filters for numeric or date fields
Include aggregations in the response
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 33 agents privately built on Nagent that already use Elasticsearch.
Build on Nagent
Connect Elasticsearch to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Elasticsearch, and click "Connect Now." You'll authenticate with API_KEY, BASIC — Nagent handles credential storage and refresh automatically. Once connected, Elasticsearch is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Elasticsearch is connected, you configure its 4 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Elasticsearch steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Elasticsearch event fires, the agent kicks off automatically.
Every Elasticsearch action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Elasticsearch ships with 4 pre-built databases actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Elasticsearch together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Elasticsearch-based workflows tailored to your business.