MongoDB database
Mongodb is the document database that backs a huge range of apps, from user profiles to event logs to product catalogs. The NoClick Mongodb node connects over your cluster's connection string and can run aggregation pipelines, write documents in bulk, delete them one at a time or in batches, count documents, and pull distinct values. It also runs Atlas Text Search and Atlas Facet Search, creates and drops standard, Atlas Search, and vector search indexes, and can send raw database commands with Run Command. Drop it onto the canvas to move data in and out of Mongodb on a schedule or in response to any event, with no glue scripts to maintain.
Yes. The node runs aggregation pipelines to read and shape data, writes and updates documents in bulk with Bulk Write, and removes them with Delete One Document or Delete Many Documents. Wire any of these to a trigger so a schedule, a form, or an inbound message drives real database changes.
It does. You can run Atlas Text Search and Atlas Facet Search over your collections, and create the indexes behind them, including a vector search index for semantic and embedding-based queries. Create Atlas Search Index and Delete Search Index let you manage those search indexes from the same workflow.
The node authenticates with your Mongodb connection string, so it works with Atlas or any self-hosted cluster that URI can reach. Add it once as a credential and every operation in the workflow reuses it.
The Mongodb node is request/response, so it does not emit its own trigger events. Pair it with a schedule or another trigger node, then use Count Documents or Estimated Document Count to detect growth and act on the result.
Yes. Run Command sends a raw Mongodb database command, so admin tasks and less common queries are still reachable. You also get collection and database management through Create Collection, Drop Collection, and Drop Database.