Menu

Mattering Automations MongoDB Atlas integration

Connect MongoDB Atlas to Mattering Automations: cluster lifecycle with pause and resume, Flex clusters, database users, the IP access list, cloud backup snapshots and restore jobs, alerts, activity events, and process and disk measurements as workflow steps, authenticated with one organization API key pair.

The Mattering Automations MongoDB Atlas integration adds the Atlas Administration API v2 to your automation canvas: list and manage organizations and projects, run the dedicated cluster lifecycle from create through update, pause, resume, and delete, manage Flex clusters (the current low-cost generation that replaced serverless instances), create and manage database users, control the project IP access list, read cloud backup snapshots and run restore jobs, triage alerts with a reversible acknowledge, read alert configurations, pull project and organization activity events, and read process and disk measurements as timeseries data.

The credential is an organization API key pair created in the Atlas console and sent over HTTP Digest: the public key acts as the username, the private key as the password. MongoDB's documentation describes API keys as a legacy authentication method and recommends service accounts for new integrations, but keys remain fully supported with no announced sunset, and the static two-field pair is what this integration stores. Setup takes a few minutes once the key exists, and this guide walks through each step, including the roles and IP access list decisions that trip people up later, and ends with the full node reference.

The safety modeling is stated on the nodes rather than buried. Of the 44 nodes, 28 read and 16 act, and five carry a destructive flag: MongoDB Atlas: Delete Project, MongoDB Atlas: Delete Cluster, MongoDB Atlas: Delete Flex Cluster, MongoDB Atlas: Delete Database User, and MongoDB Atlas: Create Restore Job, because an automated or point-in-time restore replaces all data on the target cluster. Some surfaces are deliberately absent: API key creation stays an operator act (the integration only lists keys), alert configuration rules are read-only because a mis-authored matcher can silently disable paging, serverless instances are omitted because MongoDB deprecated them in favor of Flex, and the documents inside your databases are out of scope entirely.

Before you start

  • A MongoDB Atlas account with an organization. The Administration API and organization API keys are available on Atlas accounts generally, and most of the read surface can be exercised against a free M0 cluster.
  • Permission to create API keys in your Atlas organization: creating an organization API key requires the Organization Owner role. If you cannot create keys from the organization's Applications page, ask an organization owner to create the key or grant you the role.
  • A project with at least one cluster for the cluster, backup, and measurement nodes. Pause, resume, and cloud backups apply to dedicated clusters (M10 and larger); Flex clusters have their own list, get, create, and delete nodes.
  • A Mattering workspace with access to the Automations app.
  • Your organization ID and project ID handy, or plan to fetch them with MongoDB Atlas: List Organizations and MongoDB Atlas: List Projects as first steps: the project ID feeds every project-scoped node.

Create a MongoDB Atlas organization API key

Mattering authenticates to Atlas with an organization API key pair over HTTP Digest: the public key is the username, the private key is the password, and both halves are required on every request. The key's roles decide what the nodes can do, so create it with the least privilege your workflows need: a read-only role is enough for monitoring and audit workflows, while lifecycle workflows need roles that can modify the projects and clusters they touch.

Sign in at cloud.mongodb.com, select the organization, and click Applications in the sidebar under the Identity & Access section.
Click Add new API Key. Give the key a description your future self will recognize and assign the organization roles it needs.
Copy the private key now. Atlas shows it once, at creation; after you leave this screen it can never be viewed again (MongoDB Atlas: List API Keys returns it partially redacted), and your options are rolling the key or creating a new one.
Copy the public key as well. It is not a secret: it stays visible in the console, appears in API key listings, and serves as the Digest username.
If your organization requires an IP access list for Administration API keys, or you want to restrict the key yourself, add the addresses your calls will come from in the key's access list step.
An IP-restricted key returns a 403 from any other address. That is the most common reason a key that worked in one place fails in another: the credential is fine, the caller's address is not on the key's list.

Connect MongoDB Atlas to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose MongoDB Atlas from the list.
Click Create new credential, enter the public key and the private key, and save.
The credential is stored encrypted in Google Secret Manager and never appears in workflow logs. Only the private key is treated as a secret; the public key is a username that legitimately appears in API key listings.
Click Test Connection. Mattering calls the Atlas organizations endpoint, the cheapest authenticated read on the API, driving the full HTTP Digest handshake with the versioned Accept header Atlas requires. Success proves the key pair; a 403 with a correct key usually means the key carries an IP access list that does not include the address the call came from.
Click Connect. All 44 MongoDB Atlas nodes appear in your canvas palette.

Verify it works

After connecting, open any automation canvas and check the palette: a MongoDB Atlas section should list the query and action nodes. Drop MongoDB Atlas: List Organizations onto the canvas and run a test step. It is the integration's health check: the cheapest authenticated read on the whole API, it returns the organizations the key can access with their ids and names, and the organization ID from it feeds the org-scoped nodes (events, teams, API key listing). If this node succeeds, the credential is healthy; anything failing after it is a roles or parameters question, not an authentication one.

Next, run MongoDB Atlas: List Projects and copy a project ID, because every project-scoped node (clusters, database users, access lists, backups, alerts, events, and measurements) needs one. From there the pickers cascade: choosing a project fills the cluster picker from MongoDB Atlas: List Clusters, and choosing a cluster fills the snapshot picker from MongoDB Atlas: List Backup Snapshots. Note that Atlas addresses clusters by name, not by an id, which is why the cluster pickers show and submit names. Everything in this verify path is read-only: it cannot reach the five destructive nodes or change a single setting, so it is safe to re-run whenever you rotate the key.

Node reference

44 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 28

MongoDB Atlas: Get Access List Entry

mongodb_atlas_get_access_list_entry

Get one access list entry by its value - the IP address (192.0.2.10), CIDR block (192.0.2.0/24), or AWS security group ID exactly as it appears in the list. The runner URL-encodes the value (slashes in CIDR blocks encode cleanly).

MongoDB Atlas: Get Alert

mongodb_atlas_get_alert

Get one alert's details: status, event type, current metric value, the cluster or host it fired on, and acknowledgement state.

MongoDB Atlas: Get Alert Configuration

mongodb_atlas_get_alert_configuration

Get one alert configuration's full rule: event type, enabled flag, matchers, metric threshold, and notification channels.

MongoDB Atlas: Get Backup Snapshot

mongodb_atlas_get_backup_snapshot

Get one cloud-backup snapshot's details: status, creation and expiry times, MongoDB version at snapshot time, and storage size.

MongoDB Atlas: Get Cluster

mongodb_atlas_get_cluster

Get one cluster's full configuration by name: state, version, paused flag, backup settings, connection strings, and replication specs. Poll stateName (IDLE / CREATING / UPDATING / REPAIRING / DELETING) to wait for a change to land.

MongoDB Atlas: Get Database User

mongodb_atlas_get_database_user

Get one database user by auth database and username: roles, scopes, and external-auth type flags. The password is never returned.

MongoDB Atlas: Get Disk Measurements

mongodb_atlas_get_disk_measurements

Get timeseries disk measurements for one partition on a process host: free and used space, IOPS, and latency, at a chosen granularity. Same window rules as process measurements: set EITHER period OR start+end - never both.

MongoDB Atlas: Get Flex Cluster

mongodb_atlas_get_flex_cluster

Get one Flex cluster's details by name: state, MongoDB version, backing provider and region, backup settings, and connection strings.

MongoDB Atlas: Get Organization

mongodb_atlas_get_organization

Get one organization's details by ID: name, deletion state, and default-alert-settings flag.

MongoDB Atlas: Get Process Measurements

mongodb_atlas_get_process_measurements

Get timeseries measurements for one MongoDB process: connections, opcounters, CPU, memory, cache activity, and more, at a chosen granularity. Each measurement returns dataPoints of timestamp/value pairs. Set EITHER period (rolling lookback) OR start+end (fixed window) - never both. The core observability read for threshold checks and reporting automations.

MongoDB Atlas: Get Project

mongodb_atlas_get_project

Get one project's details by ID: name, owning organization, cluster count, and creation date.

MongoDB Atlas: Get Team

mongodb_atlas_get_team

Get one team's details by ID (id and name; member listing is a separate users endpoint outside this connector's scope).

MongoDB Atlas: List API Keys

mongodb_atlas_list_api_keys

List an organization's programmatic API keys with their descriptions, public keys, and role assignments - the credential audit read. Atlas partially redacts each privateKey in this response; full private keys are shown exactly once at creation in the UI. Key creation is deliberately not available through this connector.

MongoDB Atlas: List Access List Entries

mongodb_atlas_list_access_list_entries

List the project's IP access list: the IP addresses, CIDR blocks, and AWS security groups allowed to connect to the project's clusters, with comments and any auto-expiry dates.

MongoDB Atlas: List Alert Configurations

mongodb_atlas_list_alert_configurations

List a project's alert configurations (the rules that fire alerts) with event types, matchers, thresholds, and notification channels. Read-only surface by scope - authoring alert rules stays in the Atlas UI.

MongoDB Atlas: List Alerts

mongodb_atlas_list_alerts

List a project's alerts with status, event type, the triggering metric and value, and acknowledgement state. Filter by status OPEN, TRACKING, or CLOSED. The alert ID from here feeds Get Alert and Acknowledge Alert.

MongoDB Atlas: List Backup Snapshots

mongodb_atlas_list_backup_snapshots

List a cluster's replica-set cloud-backup snapshots with creation and expiry times, status, type (scheduled or onDemand), and storage size. The snapshot ID from here feeds Get Backup Snapshot and Create Restore Job. Covers replica-set clusters; sharded-cluster snapshots live on a separate endpoint that is out of scope.

MongoDB Atlas: List Clusters

mongodb_atlas_list_clusters

List the dedicated clusters in a project with their names, states, MongoDB versions, paused flags, connection strings, and replication specs. The cluster NAME from here addresses every other cluster node - Atlas has no cluster-id path.

MongoDB Atlas: List Database Users

mongodb_atlas_list_database_users

List the database users in a project with their auth databases, roles, and cluster scopes. Passwords are never returned. The username from here feeds the get / update / delete user nodes.

MongoDB Atlas: List Disks

mongodb_atlas_list_disks

List the disk partitions on one MongoDB process host (typically a data partition). The partition name from here feeds Get Disk Measurements.

MongoDB Atlas: List Flex Clusters

mongodb_atlas_list_flex_clusters

List the Flex clusters in a project (the low-cost tier that replaced serverless instances) with names, states, provider settings, and connection strings. Dedicated clusters live on List Clusters instead.

MongoDB Atlas: List Organization Events

mongodb_atlas_list_organization_events

List an organization's activity events (billing changes, membership changes, project creation) filtered by date range and event types. Append-only audit entries at org scope.

MongoDB Atlas: List Organizations

mongodb_atlas_list_organizations

List the organizations the API key can access with their ids and names. The cheapest authenticated read on the whole API and the credential health check to run first in any Atlas automation - the organization ID from here feeds the org-scoped nodes (events, teams, API keys).

MongoDB Atlas: List Processes

mongodb_atlas_list_processes

List the MongoDB processes (mongod and mongos nodes) running in a project, each identified as hostname:port with its role (REPLICA_PRIMARY, REPLICA_SECONDARY, SHARD_MONGOS...). The process ID from here feeds the measurement and disk nodes.

MongoDB Atlas: List Project Events

mongodb_atlas_list_project_events

List a project's activity events (cluster changes, user actions, alert firings) filtered by date range, event types, or cluster names. Events are append-only audit entries - the compliance and change-feed read.

MongoDB Atlas: List Projects

mongodb_atlas_list_projects

List the projects (Atlas 'groups') the API key can access across all its organizations, with ids, names, org ids, and cluster counts. The project ID from here feeds every project-scoped node: clusters, database users, access lists, backups, alerts, events, and measurements.

MongoDB Atlas: List Restore Jobs

mongodb_atlas_list_restore_jobs

List a cluster's backup restore jobs with delivery type, source snapshot, target cluster, and completion state. The monitoring read for restore automations - poll until finishedAt is set or failed flips true.

MongoDB Atlas: List Teams

mongodb_atlas_list_teams

List an organization's teams with their ids and names. Teams group Atlas users for project role assignment; the team ID from here feeds Get Team.

Action nodes 16

MongoDB Atlas: Acknowledge Alert

mongodb_atlas_acknowledge_alert

Acknowledge an alert until a chosen time (notifications pause until then) or un-acknowledge it by sending unacknowledgeAlert true. Fully reversible - the alert record itself is untouched.

MongoDB Atlas: Add Access List Entries

mongodb_atlas_add_access_list_entries

Add one or more entries to the project's IP access list. The request body is an ARRAY of entry objects; each entry carries exactly one of ipAddress, cidrBlock, or awsSecurityGroup, plus an optional comment and an optional deleteAfterDate for temporary access (max 7 days out). Reversible - Delete Access List Entry removes an entry.

MongoDB Atlas: Create Cluster

mongodb_atlas_create_cluster

Create a dedicated cluster in a project. Provisions billable cloud infrastructure that keeps running until deleted - pair test creates with Delete Cluster. Creation is asynchronous: the response returns stateName CREATING and the cluster becomes usable minutes later (poll Get Cluster).

MongoDB Atlas: Create Database User

mongodb_atlas_create_database_user

Create a database user in a project. Users apply to every cluster in the project unless narrowed with scopes. Reversible - Delete Database User removes it. Supports temporary users via deleteAfterDate (auto-removed at that time, max 7 days out).

MongoDB Atlas: Create Flex Cluster

mongodb_atlas_create_flex_cluster

Create a Flex cluster in a project - the low-cost tier for development and small workloads. Provisions a billable resource that runs until deleted; pair test creates with Delete Flex Cluster. Creation is asynchronous (stateName CREATING, then IDLE).

MongoDB Atlas: Create Project

mongodb_atlas_create_project

Create a new project inside an organization. Projects are the container for clusters, database users, and network access rules. Reversible - Delete Project removes an empty project cleanly.

MongoDB Atlas: Create Restore Job

mongodb_atlas_create_restore_job

DESTRUCTIVE: restore a snapshot. With deliveryType automated or pointInTime this REPLACES ALL DATA on the target cluster with the snapshot's data; deliveryType download instead produces a download URL and touches nothing. cluster_name is the SOURCE cluster whose backup is restored; the target fields say where the data lands.

MongoDB Atlas: Delete Access List Entry

mongodb_atlas_delete_access_list_entry

Remove one entry from the project's IP access list by its value (IP address, CIDR block, or AWS security group ID). Clients connecting from that range are refused until it is re-added; recreating the entry is a single Add call with the same value.

MongoDB Atlas: Delete Cluster

mongodb_atlas_delete_cluster

DESTRUCTIVE: permanently delete a cluster and all data on it. Set retainBackups true to keep existing cloud-backup snapshots after the cluster is gone (restorable into a new cluster); otherwise snapshots are deleted too. Refused while terminationProtectionEnabled is true. Deletion is asynchronous (202 Accepted).

MongoDB Atlas: Delete Database User

mongodb_atlas_delete_database_user

DESTRUCTIVE: delete a database user. Applications authenticating as this user lose access immediately. The user record is recreatable but its password is not recoverable, so recreation means issuing a new credential.

MongoDB Atlas: Delete Flex Cluster

mongodb_atlas_delete_flex_cluster

DESTRUCTIVE: permanently delete a Flex cluster and all data on it. Refused while terminationProtectionEnabled is true. Deletion is asynchronous (202 Accepted).

MongoDB Atlas: Delete Project

mongodb_atlas_delete_project

DESTRUCTIVE: permanently delete a project. The project must be empty first (no clusters); Atlas refuses otherwise. The project record, its access lists, database users, and alert configurations are gone irreversibly.

MongoDB Atlas: Pause Cluster

mongodb_atlas_pause_cluster

Pause a dedicated cluster (PATCH with paused true - the v2 API has no separate pause endpoint). A paused cluster stops compute billing but keeps storage; connections are refused while paused. Atlas auto-resumes a paused cluster after 30 days unless it is paused again. Resume Cluster reverses this. Only M10+ dedicated clusters can be paused, and a freshly resumed cluster must run ~60 minutes before it can pause again.

MongoDB Atlas: Resume Cluster

mongodb_atlas_resume_cluster

Resume a paused dedicated cluster (PATCH with paused false). Compute billing restarts; the cluster accepts connections again once stateName returns to IDLE.

MongoDB Atlas: Update Cluster

mongodb_atlas_update_cluster

Update a cluster's configuration: scale instance sizes via replicationSpecs, toggle backups or termination protection, change the MongoDB major version, or set tags. PATCH semantics - only the fields sent change. Use the dedicated Pause Cluster / Resume Cluster nodes for the paused flag. Changes apply asynchronously (poll Get Cluster).

MongoDB Atlas: Update Database User

mongodb_atlas_update_database_user

Update a database user's password, roles, scopes, or description. Only the fields sent change. The username and auth database cannot be changed - delete and recreate for that.

Using the integration

On the automation canvas

MongoDB Atlas nodes chain with every other node: a schedule can run MongoDB Atlas: Pause Cluster across development clusters each evening and post what it paused to a channel, a metrics sweep can read MongoDB Atlas: Get Process Measurements and write drift into a Mattering database, and MongoDB Atlas: List Alerts can feed a triage workflow that opens tasks in Mattering Productivity. The project ID from MongoDB Atlas: List Projects is the value almost every downstream node asks for, and the organization ID from MongoDB Atlas: List Organizations covers the rest.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and Matter can drive the same surface. An agent can list a project's clusters with MongoDB Atlas: List Clusters, check their health with MongoDB Atlas: Get Process Measurements, acknowledge a noisy alert with MongoDB Atlas: Acknowledge Alert, and open temporary access with MongoDB Atlas: Add Access List Entries. The read nodes are the safest surface to hand an agent; keep the five destructive nodes behind conditions or approval steps.

Cluster lifecycle and cost control

MongoDB Atlas: Pause Cluster stops a dedicated cluster's compute billing while keeping its storage, and MongoDB Atlas: Resume Cluster reverses it, which makes the pair safe to hand to a schedule. The operational facts live on the nodes: only M10 and larger dedicated clusters pause, Atlas auto-resumes a paused cluster after 30 days unless it is paused again, and a freshly resumed cluster must run about 60 minutes before it can pause again. MongoDB Atlas: Update Cluster handles scaling and settings with PATCH semantics, so only the fields you fill change, and every cluster change is asynchronous: poll MongoDB Atlas: Get Cluster until stateName returns to IDLE before treating the change as landed.

Temporary access that expires on its own

MongoDB Atlas: Add Access List Entries opens the project IP access list for one or more addresses, CIDR blocks, or AWS security groups, each with an optional deleteAfterDate up to 7 days out, so short-lived grants revoke themselves. MongoDB Atlas: Create Database User supports the same deleteAfterDate for temporary users, and scopes narrow a user to specific clusters instead of the whole project. MongoDB Atlas: List Access List Entries and MongoDB Atlas: List Database Users are the audit reads that show what access currently exists, and passwords are never returned by any node.

Measurements and the window rules

MongoDB Atlas: List Processes identifies each mongod and mongos process as hostname and port with its replica role, and that process ID feeds MongoDB Atlas: Get Process Measurements, MongoDB Atlas: List Disks, and MongoDB Atlas: Get Disk Measurements. Both measurement nodes follow the same API rules: granularity is required as an ISO 8601 duration such as PT1M or PT1H, and the window is either a rolling period or a fixed start and end pair, never both in one request. Results arrive as one series per requested measurement, each a list of timestamp and value pairs, which drops cleanly into a Mattering database for trending and threshold checks.

The five destructive nodes, gated

MongoDB Atlas: Create Restore Job is the one people underestimate: with deliveryType automated or pointInTime it replaces all data on the target cluster, which is the purpose of a restore and exactly why it belongs behind an approval task; the download delivery type instead produces a download URL and touches nothing. MongoDB Atlas: Delete Cluster and MongoDB Atlas: Delete Flex Cluster permanently remove a cluster and its data, though cluster delete can set retainBackups to keep snapshots, and both refuse to run while termination protection is enabled. MongoDB Atlas: Delete Database User cuts off applications immediately and the password is not recoverable, and MongoDB Atlas: Delete Project only works on an empty project but takes its access lists, users, and alert configurations with it irreversibly. The pattern for all five is the same: read the thing first, and put the node behind a condition, an approval task, or a manual run rather than a bare trigger.

Troubleshooting

Test Connection fails with an authentication error
Digest authentication needs both halves of the key pair in the right fields: the public key is the username, the private key is the password, and swapping them fails exactly like a wrong key. Check both values for whitespace picked up in the copy, and confirm the key was not deleted or rolled in the Atlas console. One internal detail worth knowing: the Digest handshake's first leg is always a 401 challenge, even on success, and Mattering only reports the final response, so a surfaced authentication failure means the key pair itself was refused.
The key is correct but calls return 403
Two separate causes look identical here. First, the key may carry an IP access list, either added at creation or required by an organization setting, and a restricted key returns 403 from any address not on it: open the key on the organization's Applications page and add the caller's address. Second, the key's roles may not cover the operation: a read-only key passes Test Connection and every list node, then gets refused by writes. Roles are edited on the key from the same Applications page without recreating it.
Pause Cluster is refused or errors
Only dedicated clusters at M10 and larger can pause; M0 free clusters and Flex clusters cannot, so a pause sweep should filter to dedicated clusters first. Timing matters too: a freshly resumed cluster must run about 60 minutes before it can pause again, so a resume followed immediately by a pause fails. And note that Atlas auto-resumes any paused cluster after 30 days; that is documented Atlas behavior, not a defect, and a scheduled re-pause is the standard answer for clusters meant to stay down longer.
The measurement nodes reject the request
The window parameters are mutually exclusive: send either period (a rolling lookback) or start and end (a fixed window), never both, or Atlas rejects the request. Granularity is required and must be an ISO 8601 duration such as PT1M, PT1H, or P1D. The process ID must be the hostname and port value exactly as MongoDB Atlas: List Processes returns it. If the request succeeds but data points come back sparse or empty, check the window against the cluster: Atlas retains metrics for a limited time per granularity, so fine-grained data is only available for recent windows.
Delete Cluster or Delete Flex Cluster is refused
A cluster with termination protection enabled refuses deletion by design. For dedicated clusters, disable it with MongoDB Atlas: Update Cluster by setting terminationProtectionEnabled to false, then delete; for Flex clusters the integration deliberately ships no update node, so disable termination protection in the Atlas console first. Deletion is also asynchronous: Atlas accepts the request and the cluster passes through a DELETING state, so poll MongoDB Atlas: List Clusters or MongoDB Atlas: Get Cluster until it is gone before running steps that depend on the deletion.
Delete Project fails
Atlas refuses to delete a project that still contains clusters, so the teardown order is fixed: delete the clusters, poll until they are actually gone (cluster deletion is asynchronous), then delete the project. Once the project delete succeeds it is irreversible, and it takes the project's access list entries, database users, and alert configurations with it, which is why the node carries a destructive flag and belongs behind a gate in any automated teardown.
Get Access List Entry or Delete Access List Entry returns not found
The entry value must match exactly as it appears in the list: an entry stored as a CIDR block is not found by its bare IP address, and vice versa. Run MongoDB Atlas: List Access List Entries and copy the value from whichever field the entry actually uses (ipAddress, cidrBlock, or awsSecurityGroup). Pass the value in plain form; the integration URL-encodes it on the wire, so the slash in a CIDR block is handled for you.
Nodes start returning 429 during a large sweep
Atlas rate-limits the Administration API per endpoint set rather than with one global number, and requests over a limit return HTTP 429 with rate-limit headers. The nodes report the 429 on their output rather than silently retrying, so add a wait step between bursts, spread scheduled sweeps apart, and cut the request count with pagination: list endpoints accept up to 500 items per page, which usually turns a burst of Get calls into one List call.

MongoDB Atlas is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.

Start Free Explore our Products