[ Developer tools ]
MongoDB integration for your workflows.
Connect MongoDB to Collabase once and use 7 actions in your workflows. No code needed, hosted in Switzerland.
MongoDB in Collabase
Connect MongoDB to Collabase once and use 7 actions in your workflows. No code needed, hosted in Switzerland.
How to connect it
- Open the integrations in the workspace settings.
- Choose MongoDB and connect your account.
- Add a trigger or an action to the workflow.
MongoDB triggers
MongoDB does not start a workflow on its own. You use its actions after any other trigger.
MongoDB actions
| Name | Description | Fields |
|---|---|---|
| Find Documents | Find documents in a collection |
+ 1
|
| Insert Documents | Insert one or more documents into a collection |
|
| Update Documents | Update multiple documents in a collection |
|
| Delete Documents | Delete documents from a collection |
|
| Find and Update Documents | Find documents and update them, returning the updated documents |
|
| Find and Replace Documents | Replace documents that match a filter with a new document |
|
| Aggregate Documents | Perform aggregation operations on documents in a collection |
|
[ Developer tools ]
Related integrations
Tools that often share a workflow.
Questions about MongoDB
What can I automate with MongoDB in Collabase?
MongoDB brings 7 actions and 0 triggers, for example Find Documents, Insert Documents, Update Documents, Delete Documents and 3 more. You combine them in a workflow without code and mix them with every other integration.
How do I connect MongoDB to Collabase?
You open the integrations in the workspace settings, choose MongoDB and connect your account once, using custom credentials. After that all triggers and actions are available in the workflow.
Does the MongoDB integration cost extra?
No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.
Test it against your own content. A proof of concept is ready within days.
We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.