MongoDB Triggers

Currently, Connect iPaaS provides five triggers for MongoDB. The MongoDB triggers on Connect iPaaS are real-time triggers which means that MongoDB will notify Connect iPaaS as soon as any changes are made in the desired document or collection.

Note: As we are using change stream mechanism to get the notification from the database this mechanism does not support system databases like admin, config and local. And you should have replication enabled for this database.

1. Collection Dropped
2. Document Created
3. Document Deleted
4. Document Updated

Figure 1. Triggers for MongoDB Application on Connect iPaaS

Collection Dropped

It triggers your workflow when a collection is dropped from the MongoDB database. Optionally, you can also apply filters while defining the trigger.

Figure 2. Setting up MongoDB Collection Dropped Trigger on Connect iPaaS

Document Created

It triggers your workflow when a new document is added to the MongoDB database collection.

For example in Figure 4 below, when the document is created inside testcollection collection then connect iPaaS will get a notification. You can also use event filters to filter out specific event.

Figure 3. Setting up MongoDB Document Created Trigger on Connect iPaaS

Document Deleted

It triggers your workflow when the document is deleted from the MongoDB database collection.

For example in Figure 5 below, when the document is deleted from testcollection collection then connect iPaaS will get a notification. You can also use event filter to filter out specific event.

Figure 4. Setting up MongoDB Document Deleted Trigger on Connect iPaaS

Document Updated

It triggers your workflow when the document is updated to the MongoDB database collection.

For example in Figure 6 below, when the document is updated from testcollection collection then connect iPaaS will get a notification. You can also use event filter to filter out specific event.

Figure 5. Setting up MongoDB Document Updated Trigger on Connect iPaaS