This topic was automatically generated from Slack. You can find the original thread here.
How can I listen to a change in MongoDB?
To listen for changes in MongoDB, you can use the Pipedream MongoDB triggers. For example, you can use the “New Document” trigger to listen for new documents in a specific collection. Here’s how to set up the “New Document” trigger: 1. Search for the MongoDB app from the trigger menu 2. Select the New Document trigger 3. Connect your MongoDB account 4. Select a Database or pass a string from a previous step. 5. Select a Collection or pass a string from a previous step. 6. Follow the instructions on the trigger configuration screen. You may need to generate a test event from MongoDB to get real data to test your workflow. For other MongoDB triggers, you can follow similar steps.
I want to listen to a specific change and not when a new document created
I understand that you want to listen for a specific change in MongoDB. Currently, Pipedream doesn’t have a built-in trigger for listening to specific changes in a document. However, you can create a custom trigger using Pipedream’s Node.js code steps to poll the MongoDB collection and check for changes based on your criteria. To do this, you can use the “Run Node.js code with $end” trigger and set up a polling interval. Then, in the code step, you can connect to your MongoDB instance, query the collection, and compare the results to detect the specific change you’re interested in. If you need help with writing the custom code, please provide more details about the specific change you want to listen for, and I’ll be happy to help.
I don’t want to pull data from MongoDB in interval time.
I want to set a custom trigger that will be triggered instantly as a change occurred
I understand that you want to set up a custom trigger that reacts instantly to changes in MongoDB. Unfortunately, Pipedream doesn’t currently support real-time change stream triggers for MongoDB. However, you can consider using MongoDB’s change streams feature in your own application to listen for changes and then send an HTTP request to a Pipedream workflow using an HTTP trigger. This way, your Pipedream workflow will be triggered instantly when a change occurs in MongoDB. Here’s a high-level overview of the steps: 1. Create a new Pipedream workflow with an HTTP trigger. 2. In your own application, set up a MongoDB change stream listener using the MongoDB driver or a library that supports change streams. 3. When a change occurs, send an HTTP request from your application to the Pipedream workflow’s endpoint (provided by the HTTP trigger). 4. In your Pipedream workflow, process the incoming data and perform any desired actions. Remember that this approach requires you to implement the change stream listener in your own application, outside of Pipedream. If you need help with setting up the change stream listener or sending HTTP requests to Pipedream, please provide more details about your application’s programming language and environment, and I’ll be happy to help.
I use MongoDB hosted by Digitalocean, how can I do that?
To set up a real-time change stream listener for your MongoDB hosted on DigitalOcean, you can follow these steps: 1. Create a new Pipedream workflow with an HTTP trigger. 2. In your own application, set up a MongoDB change stream listener using the MongoDB driver or a library that supports change streams. You’ll need to connect to your DigitalOcean-hosted MongoDB instance using the connection string and credentials provided by DigitalOcean. 3. When a change occurs, send an HTTP request from your application to the Pipedream workflow’s endpoint (provided by the HTTP trigger). 4. In your Pipedream workflow, process the incoming data and perform any desired actions. Please note that this approach requires you to implement the change stream listener in your own application, outside of Pipedream. If you need help with setting up the change stream listener or sending HTTP requests to Pipedream, please provide more details about your application’s programming language and environment, and I’ll be happy to help.
You should build it in Pipedream
Thank you for your suggestion! I’ll forward your request to the Pipedream team for consideration. In the meantime, if you have any other questions or need assistance with Pipedream, feel free to ask.
See above, I agree that we should add a Mongo trigger for any changes to a document. I believe we can programmatically create / ingest events from the change stream Pi refers to above. https://www.mongodb.com/docs/manual/changeStreams/