Skip to main content


The Enterspeed Elasticsearch integration uses the destinations field to send data from views directly to a configured Elasticsearch. This means that you can decide on the schema level which views you want to send to Elasticsearch cluster.

You will only have to set the destination field on the entity schema you want to send to Elasticsearch. It's possible to configure multiple Elasticsearch destinations if you need to push different types of data to different Elasticsearch clusters or indexes.


In order to setup the Elasticsearch configuration you need the following:

Elasticsearch endpointThe endpoint of Elasticsearch cluster you want to integrate to
API KeyThe API key used for calling Elasticsearch _bulk endpoint for creating, updating, deleting documents
Index nameName of the default index to use when creating, updating, deleting documents in Elasticsearch.
Enterspeed Environment Client API KeyThe API key for an Enterspeed Environment client. This is used to fetch the view that will be inserted into Elasticsearch


Table of available options, that you can optionally specify, if needed for your use case.

documentIdBy default Enterspeed uses view id as the value for document id in elasticsearch. You can override default document id by providing value for this option.
indexNameOption to override what index must be used for current view. By default IndexName of Elasticsearch configuration is used.

Example of usage

Schema with elasticsearch destination
/** @type {Enterspeed.FullSchema} */
export default {
triggers: function(context) {
context.triggers('geodata', ['city']);
actions: function (sourceEntity, context) {
documentId: `city-${sourceEntity.originId}`,
indexName: 'cities'
properties: function ({url, properties: p}, context) {
return {
url: url,
population: parseInt(p.population),
location: `${},${p.lng}`,