Skip to content
ClickRuntime

Automate MongoDB

Watch your MongoDB Atlas organization the way an ops lead would: open alerts, the cluster list, backup snapshots, IP access lists and the pending invoice. These automations read the Atlas Admin API on a schedule and report what needs attention. Say what you want checked to your AI assistant, confirm the steps it proposes, and the report arrives on time from then on.

Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Try asking

Create a ClickRuntime automation: every weekday at 8am, list the open alerts in all my MongoDB Atlas projects and email me each one with the project, cluster, alert type and when it started.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Ideas

What you can automate in MongoDB

A morning list of open alerts, a weekly record of clusters and their tiers, a running view of what Atlas costs, warnings about missing backups, and a flag on any project open to the whole internet. These are ready-made starting points. Anything else you can describe works too.
Daily

Get open Atlas alerts every morning

Each morning one email lists every alert still open across your Atlas projects.

See how it works
Weekly

Keep a weekly list of your Atlas clusters

Every Monday you get each cluster's project, tier, MongoDB version and state in one table.

See how it works
Weekly

Track what Atlas is costing this month

Once a week you see the running total of your pending Atlas invoice and its biggest line items.

See how it works
Daily

Get warned when a cluster backup is missing

You hear about any backed-up cluster whose newest snapshot failed or is more than a day old.

See how it works
Weekly

Audit Atlas IP access lists weekly

Each week you see who can reach every project, with open-to-all entries and new additions called out.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with MongoDB, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any MongoDB automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what MongoDB should do in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.

  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every 10 minutes, check my MongoDB jobs collection for jobs that have been in processing for more than 20 minutes and reset them to queued.

Every morning, copy yesterday's new documents from my MongoDB leads collection into a Google Sheet.

Every week, run an aggregation on my MongoDB orders collection for revenue by product, write it to Google Sheets, and post the top 5 to Slack.

Beyond chat

Have MongoDB work when you're not in the chat

Connecting MongoDB to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect MongoDB

MongoDB connects through an Atlas service account that you create in your own organization. You choose its roles, so a read-only account is enough for every report here except billing, which needs a billing viewer role.

MongoDB

Developer / Database

  1. In Atlas, open your organization's Access Manager, go to Applications and then Service Accounts, and click Create.
  2. Name it, give it roles such as Project Read Only (and Organization Billing Viewer for invoice summaries), and pick a secret expiry.
  3. Copy the Client ID and Client Secret before you close the page.
  4. In the ClickRuntime dashboard, open Connections and enter the Client ID and Client Secret for MongoDB.

Good to know

MongoDB limits that affect automations

  • The Admin API manages Atlas resources such as projects, clusters, alerts and backups. It does not read or write documents in your collections; that needs a database user and a connection string.
  • Organizations created in the Atlas UI require an API access list for the Admin API, and calls from addresses not on it are refused with a 403.
  • Backup checks only cover clusters with Cloud Backup turned on, which means M10 and larger; Flex clusters keep their snapshots elsewhere.
  • The service account secret has the expiry you set when creating it, so plan to replace it before that date.

FAQ

Questions about automating MongoDB

Can ClickRuntime read the data inside my MongoDB collections?
Not with this connection. The service account talks to the Atlas Admin API, which covers projects, clusters, alerts, backups, access lists and billing, not the documents themselves.
Which roles should the service account have?
`Project Read Only` covers alerts, clusters, snapshots and access lists. Add `Organization Billing Viewer` only if you want the invoice summary.
Why does the Admin API return 403 errors?
Atlas organizations created in the UI enforce an API access list for the Admin API. Requests from addresses not on that list are rejected, so check the list in your organization settings.
What does the access list audit flag?
Any project that allows `0.0.0.0/0`, which means anyone on the internet can try to connect, and any entries added since the previous week's check.
Do these Atlas reports need an AI key?
No. They are straight API reads and comparisons. If you want an alert explained in plain words, that uses the AI already included in your ClickRuntime plan.
Is this a MongoDB connector for ChatGPT or Claude?
Not for chatting with MongoDB data. A chat connector lets your assistant read and change MongoDB while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each MongoDB event.

Related pages

Keep exploring

Tell your assistant what MongoDB should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude