# Elasticsearch insert triggers
**URL:** https://discuss.elastic.co/t/elasticsearch-insert-triggers/84860
**Category:** Elasticsearch
**Created:** [May 7, 2017, 7:52pm UTC](https://discuss.elastic.co/t/elasticsearch-insert-triggers/84860 "2017-05-07T19:52:23Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@priyaraj](https://discuss.elastic.co/u/priyaraj)
#### Post date: [May 7, 2017, 7:52pm UTC](https://discuss.elastic.co/t/elasticsearch-insert-triggers/84860/1 "2017-05-07T19:52:23Z")
Hi,
I have a use case where when a certain document is indexed, based on the fields in the newly inserted document, I would like to index another document in a different index. The expected behavior is somewhat similar to an insert trigger in SQL Server. How can this be done? What are some of the options in Elasticsearch?
Thanks for your help!
---
### Author:  [@priyaraj](https://discuss.elastic.co/u/priyaraj)
#### Post date: [May 16, 2017, 12:33am UTC](https://discuss.elastic.co/t/elasticsearch-insert-triggers/84860/2 "2017-05-16T00:33:39Z")
Hi, I am looking for information on this still. Any help is greatly appreciated. When a document comes in, would like to do the following:
1. Search another index for certain documents based on a few fields of the incoming document
2. Then create a new document which is a "derived" document and index it into a another index
3. Proceed with indexing the current incoming document
I have looked at the ingest node custom processor plugin as one of the potential options but not sure if it is capable of doing something like this and what are some of the pitfalls to watch out for?
Also is there another solution available?
Thanks
Priya
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [May 16, 2017, 4:30am UTC](https://discuss.elastic.co/t/elasticsearch-insert-triggers/84860/3 "2017-05-16T04:30:40Z")
The ingest node can as far as I know only modify the current document, not create new ones, so you will need to do this before you send the data to Elasticsearch.
---
### Author:  [@priyaraj](https://discuss.elastic.co/u/priyaraj)
#### Post date: [May 18, 2017, 3:34pm UTC](https://discuss.elastic.co/t/elasticsearch-insert-triggers/84860/4 "2017-05-18T15:34:56Z")
Thank you for your reply. Sorry for the delay. Ingest pipeline is what I was thinking to implement for this. The pipeline could have a custom processor that would do this. Can you please confirm if this is a viable solution? Would exposing a custom REST API end point in elasticsearch an option too? If both can do this, is one preferred over another?
Thanks for your time.
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [May 18, 2017, 3:36pm UTC](https://discuss.elastic.co/t/elasticsearch-insert-triggers/84860/5 "2017-05-18T15:36:30Z")
I clarified my previous response as I now realised it was confusing.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 15, 2017, 3:36pm UTC](https://discuss.elastic.co/t/elasticsearch-insert-triggers/84860/6 "2017-06-15T15:36:46Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.