Daily

Get open Atlas alerts every morning

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

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

Send this to your assistant

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.

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

A MongoDB Atlas project raises alerts for things like replica set elections, high connections, disk usage and a primary going down. They arrive by email and by whatever integration was set up, and many are acknowledged without being resolved. A developer who joins a project months later has no idea that an alert about oplog window has been open for three weeks, and open alerts across several projects are never reviewed together. Teams with several projects feel this most.

Each morning ClickRuntime lists every Atlas project your API key can see, asks for alerts with the status OPEN, and emails one summary showing the project, alert type, affected cluster and when it opened. If nothing is open, it can send nothing at all.

It is useful for small teams where nobody has a full-time database administrator.

What you get out of it

Stale alerts get a daily reminder
An alert that stays open is listed again the next morning. A disk warning at 80 percent is seen daily until fixed, instead of being forgotten after a single email.
All projects in one email
Teams with separate Atlas projects for production, staging and analytics get one list. You do not log in to three projects to learn that staging has an unresolved issue. Teams that keep separate Atlas projects for production, staging and analytics read one email and see them all.
New hires see the real state
A person taking over database duties reads the digest and knows what is open right now. They do not depend on the previous owner's memory or on a stale handover note.
Problems found before an outage
Alerts like replication lag or rising connections often come days before a failure. A morning review lets you act at a calm moment rather than during an incident. Replication lag or climbing connections often show up days before a failure, so a calm morning review beats a 3am page.
A habit of closing alerts
When open alerts show up in an email every day, people resolve or tune them. The Atlas alert list gets cleaner, so alerts that remain mean something. The remaining alerts become ones worth reading, since noisy conditions get fixed or tuned.

How it works

What happens, step by step

Every morning ClickRuntime goes through each of your MongoDB Atlas projects.
It collects every alert that is still open.
You get one email listing each alert with its project, cluster, type and when it started.

Before it runs live

Connect MongoDB

What you get

RunsDaily

Get open Atlas alerts every morningtoday, 9:00Succeeded

Email · Atlas alertsacme-prod / orders-cluster: OUTSIDE_METRIC_THRESHOLD since 2026-10-19T02:14

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_daily_digest_of_open_alerts.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"]:
        for a in atlas(f"/groups/{g['id']}/alerts", status="OPEN")["results"]:
            lines.append(f"{g['name']} / {a.get('clusterName', '-')}: {a['eventTypeName']} since {a['created'][:16]}")
    notify.email_me(f"{len(lines)} open Atlas alerts", "\n".join(lines) or "No open alerts.")
    return {"open": len(lines)}

FAQ

Common questions

What Atlas permissions does the key need?

A programmatic API key with at least Project Read Only role on each project you want covered. The key and its secret are stored as secrets in ClickRuntime, and the automation only reads alerts. Create it under Access Manager in your Atlas organization and give it only that role.

Does it include alerts that were acknowledged?

Acknowledged alerts that are still open have the status OPEN, so they are listed. Closed alerts are not, which means once a condition clears in Atlas it drops out of the next digest. An alert that clears in Atlas drops out of the next digest by itself.

Does it cover Atlas projects in other organizations?

An API key belongs to one organization, so it lists that organization's projects. To cover another, create a key there and add a second run. Projects you list explicitly are the only ones that are checked.

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 (daily). 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.

Weekly