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.

Runs: Weekly
Apps: MongoDB
AI: Not needed
Access: Project Read Only

Send this to your assistant

Create a ClickRuntime automation: every Monday at 9am, email me all my Atlas clusters grouped by project with their tier, MongoDB version and current state.

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

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

Atlas clusters multiply quietly. A developer spins up an M10 for a prototype, a contractor creates a test cluster in another region, and a paused cluster still holds storage. A year in, nobody can list what exists, which tier each runs on, and which are idle. Teams often find a forgotten production-sized cluster only when the invoice looks wrong. It is a common finding in cost reviews, and it is rarely the one anybody expected.

Every week ClickRuntime goes through each Atlas project it can access, lists the clusters with their tier, provider, region and state, such as IDLE or PAUSED, and emails the whole inventory in one message. The email is a plain list you can scan in a minute.

Engineering managers and platform owners use it as a regular reality check against their own records.

What you get out of it

An accurate list of what exists
The inventory comes from Atlas itself, so it is not a spreadsheet that went stale. When someone asks how many clusters you run, the answer is in last Monday's email.
Forgotten clusters get found
A paused or oversized test cluster shows up with its tier. You can delete it or downgrade it before it adds another month of cost. Tiers and states are shown, so a paused or oversized test cluster stands out and can be deleted or downgraded before another month of charges.
Tier changes are visible
If a cluster moved from M10 to M30 during the week, the next email shows the new tier. That makes unexpected scaling a topic for discussion, not a surprise on the invoice.
Useful in security and compliance reviews
Auditors ask where data lives and on which cloud. A weekly record of cluster regions and providers helps you answer without a last-minute investigation. Auditors ask where data lives and on which cloud, so a dated weekly list of regions and providers helps you answer quickly.
Ownership questions get raised
Seeing a cluster no one recognises prompts someone to ask who made it. Regular visibility keeps shadow infrastructure from accumulating. Asking who created the odd cluster early stops shadow infrastructure from building up for a year.

How it works

What happens, step by step

Every Monday ClickRuntime goes through each of your MongoDB Atlas projects.
It lists every cluster with its tier, MongoDB version and current state.
The table arrives in your inbox, grouped by project.

Before it runs live

Connect MongoDB

What you get

RunsWeekly

Keep a weekly list of your Atlas clusterstoday, 9:00Succeeded

Email · Atlas clustersacme-prod orders-cluster: M30, MongoDB 7.0.14, IDLE

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. 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.

Changes you can ask for

Run it at a different time, more or less often, or only on weekdays
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other MongoDB steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

get_a_weekly_cluster_inventory.pyexample

from clickruntime import on_trigger, credentials, http, notify

from requests.auth import HTTPDigestAuth

ATLAS = "https://cloud.mongodb.com/api/atlas/v2"

def atlas(path, **params):
    auth = HTTPDigestAuth(credentials.secret("ATLAS_PUBLIC_KEY"), credentials.secret("ATLAS_PRIVATE_KEY"))
    resp = http.get(f"{ATLAS}{path}", auth=auth, params=params, headers={"Accept": "application/vnd.atlas.2024-08-05+json"})
    resp.raise_for_status()
    return resp.json()

@on_trigger
def run(event):
    lines = []
    for g in atlas("/groups")["results"]:
        lines.append(f"\n{g['name']}")
        for c in atlas(f"/groups/{g['id']}/clusters")["results"]:
            tier = c["replicationSpecs"][0]["regionConfigs"][0]["electableSpecs"]["instanceSize"]
            lines.append(f"  {c['name']}: {tier}, MongoDB {c['mongoDBVersion']}, {c['stateName']}")
    notify.email_me("Atlas cluster inventory", "\n".join(lines).strip())
    return {"lines": len(lines)}

FAQ

Common questions

Which cluster details does the email include?

The cluster name, project, tier or instance size, cloud provider, region and state, as reported by the Atlas Admin API. Fields like MongoDB version can be added if you need them. Cluster-level settings such as backup status are not part of the list unless you request them.

Does it cover paused and serverless instances?

Paused clusters are listed with their paused state. Serverless instances use a separate API endpoint, so tell your AI assistant if you use them and they can be included in the same email. Serverless instances are a separate resource type, so say if you use them and they can be listed too.

Can it only list what changed since last week?

Yes. By storing the previous list between runs, the email can highlight new, removed or resized clusters at the top. Many teams prefer that for large estates where the full list rarely changes. This keeps the email short when the list is long and rarely changes.

What permissions does it need?

Project Read Only. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it runs (weekly). Checks that find nothing to do and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Daily