Short answer: Drop the "Elasticsearch → Index Document" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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":"..."}" |
{"index": "{{trigger.index}}","id": "{{trigger.id}}","document": "{\"title\":\"My Doc\",\"content\":\"...\"}"}
{"_id": "1","_index": "my-index","result": "created","_version": 1}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.