Databases & CRM
Set up Elasticsearch / OpenSearch
Connect an Elasticsearch or OpenSearch cluster. Each index's mapping becomes a searchable entry — fields, types, sample values — and small record-like indices also become one record per document. Rolling log and metric indices stay schema-level entries only: half a log stream synced would be noise pretending to be knowledge. Read-only.
Before you start
- Elasticsearch: an API key with a read-only role — Kibana → Stack Management → Security → API keys → create — paste the ENCODED value it shows (an id:key pair pasted raw also works).
- OpenSearch and basic-auth clusters: a read-only user's username and password instead.
- The cluster's URL (with its port when it isn't 443) and a valid certificate — self-signed certificates aren't accepted.
- Documents → Elasticsearch / OpenSearch: enter the Cluster URL and either the API key, or a Username and Password.
- Only these indices narrows to specific indices; Skip these indices leaves particular ones out instead — blank on either reads every index that isn't a system one (names starting with a dot are always skipped).
- Choose access groups, Test, then Sync.
What comes in
- Every index as a searchable entry — its mapping's fields and types, plus a few real sample values.
- Indices that carry a name-like field and hold at most 2,000 documents also become one record per document; bigger ones keep their schema-level entry only, named in the sync summary so nothing is silently half-indexed.
| Only these indices | Allow-list, one index per line; blank reads every non-system index. |
|---|---|
| Skip these indices | The opposite — read every index except these. |
| Username / Password | Basic-auth alternative to the API key — the usual path for OpenSearch. |
Access
Visible only to the access groups chosen on the source — Elasticsearch and OpenSearch permissions aren't read or mirrored per document; the key or user's own role only caps what the connector can reach at all.
System indices (names starting with a dot) are always left out, even if listed under Only these indices. The cluster's certificate must be valid and reachable from the assistant's server — self-signed certificates fail Test.
Last updated 20 Sep 2026