ActionElasticsearchUpdated September 2026

How do I index a document in Elasticsearch?

Short answer: You can index document in Elasticsearch by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Elasticsearch Index Document action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Index Document in Elasticsearch — start free All 1 Elasticsearch actions

Index Document in Elasticsearch — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Index index	string	Required	Index
Document ID id	string	Optional	Leave empty for auto-generated ID
Document document	json	Required	Document. (JSON object). e.g. "{"title":"My Doc","content":"..."}"

Sample request

{
  "index": "{{trigger.index}}",
  "id": "{{trigger.id}}",
  "document": "{\"title\":\"My Doc\",\"content\":\"...\"}"
}

Returns

{
  "_id": "1",
  "_index": "my-index",
  "result": "created",
  "_version": 1
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Index Document.

Any of these apps can fire this action as part of a workflow.

Gmail → Elasticsearch

1 Gmail triggers

Slack → Elasticsearch

13 Slack triggers

Google Sheets → Elasticsearch

2 Google Sheets triggers

HubSpot → Elasticsearch

18 HubSpot triggers

FAQ

Questions about Index Document.

What does the Index Document action do in Elasticsearch?

Adds a JSON document to an index — Elasticsearch tokenises and indexes it for full-text search and aggregation queries. For high-volume ingestion, use the bulk endpoint via HTTP action which is much more efficient than per-document indexing.

What inputs does Index Document require?

Required: Index, Document. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Elasticsearch returns an error?

The run history shows the failed step with its input and the error message Elasticsearch returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Index Document support batch operations?

Run Index Document inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Elasticsearch's rate limits.

Index Document in Elasticsearch — start free