Elasticsearch for AI agents
Agents read Elasticsearch at once. Changes and sends are held for a person's approval by default.
About Elasticsearch
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.
What an agent can do in Elasticsearch
Every Elasticsearch action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in Elasticsearch without asking first. 4 actions.
- 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.
- 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.
- 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.
- 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.
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 0 actions.
None in this connector.
Related connectors
Elasticsearch questions
Can an agent change data in Elasticsearch on its own?
Not by default. Changes and sends in Elasticsearch are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in Elasticsearch?
This connector lists 4 read actions. Reads run at once, without waiting for approval.
How does Elasticsearch connect?
It connects with API key or Username and password. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.