MongoDB Trigger
The MongoDB trigger is used to listen on the actions or events (such as insert, update, and remove) performed on the MongoDB collections.
Note: You cannot use this trigger if you connect to Microsoft Azure Cosmos DB using Tibco Flogo MongoDB connection. This trigger uses the ChangeStream APIs to listen to any changes to the documents in a collection in real time. ChangeStream API is supported in MongoDB from 3.6 and higher versions. However Azure Cosmos DB supports MongoDB 3.4 version only.
Handler Settings
The Handler Settings section has the following fields:
Field | Description |
---|---|
Database Name | Name of the database that you want to connect in the MongoDB instance. |
Collection | Select a collection which you want to listen to. If this field is empty, then the trigger listens to all the collections in the Database. |
Listen for Insert Event | Select to listen to the insert event. |
Listen for Update Event | Select to listen to the update event. |
Listen for Remove Event | Select to listen to the remove event. |
Output
You must map the input fields of the application flow to the Trigger's output fields in the Map to Flow Inputs section. The following table lists the Trigger's output schema fields:
Field | Type | Description |
---|---|---|
Namespace | JSON Object | Displays the name of the collection and Database on which the event occurred. |
Operation Type | String | The name of event or operation that triggered the flow. |
ResultDocument | JSON Object | Lists the contents of the document on which the event occurred. In case of delete event, only the ID of the document is returned. |
Copyright © Cloud Software Group, Inc. All rights reserved.