Skip to main content
Back to list of enterprise systems Use the MongoDB integration to find, insert, update, replace, delete, and aggregate documents in a collection through Action Tools. The connector provides seven actions and no triggers.

Supported actions

Triggers

MongoDB has no triggers in the current Studio integration catalog.

Prerequisites

  • A MongoDB deployment, such as MongoDB Atlas or a self-managed server, reachable from the platform runtime.
  • A MongoDB database user with permissions for the databases and collections the selected actions need.
  • The MongoDB host, username, password, and authentication database. For Atlas SRV connections, note whether the host uses the mongodb+srv:// format.

Set up the integration

1

Prepare the MongoDB connection

Create or select a MongoDB database user and confirm it can access the target database and collections. Note the host without a protocol, username, password, and authentication database. For an Atlas mongodb+srv:// connection, enable Use Atlas SRV URL in the profile.
2

Create the auth profile

In Integrations, select MongoDB > Connect. On Project Auth Profiles, select New Profile > Integration Profile > MongoDB > Continue. Select API Key, enter the connection details, and select Create Profile. Enter the MongoDB password in the profile’s API Key field.
3

Create the action tool

In Tools, select New Tool > Action > MongoDB > Continue. Select the Action and Auth Profile, configure the inputs, and choose whether to return the complete connector response or define custom output parameters. Select Create Tool, then assign the tool to an agent.

Auth profile reference

Studio provides API Key authentication with Preconfigured usage mode. Visible to project members is enabled by default. Configure these fields: The profile also has a name and description. The Usage Mode is fixed to Preconfigured; the admin supplies credentials when setting up the profile, and end users do not authorize separately.

Action reference

Each action has an optional database string. Leave it empty to use the profile’s default database, or provide a database to override that default. The required collection field identifies the collection the action uses.
The response includes pagination values such as limit, skip, nextSkip, and hasMore.

Troubleshoot common issues