# Daily MongoDB Atlas change log with a Notion audit trail

> Every weekday at 6pm, see who changed what in your database environment, with anything risky called out and a dated record filed for compliance.

- Workflow type: agent
- Services: MongoDB Atlas, Notion, Slack Bot
- Categories: Engineering, Operations
- Published: 2026-08-07

## What it does

- Checks every one of your MongoDB Atlas projects at the end of each weekday and gathers that day's activity
- Sorts the changes into plain groups: clusters and scaling, database users and roles, network access, backups and restores, and organization or billing
- Writes a short readable summary of what happened and who did it, flagging anything that affects security or uptime, landed after hours, or touched a production cluster
- Files a dated page in your Notion compliance database and posts the headline to your engineering Slack channel with a link to it

## What you'll need

- A MongoDB Atlas login with permission to view your projects and their activity history
- A Notion workspace with a compliance database shared with General Input, where the daily pages get filed
- A Slack workspace and the channel that should receive the summary, usually #eng
- Optional: a note of which cluster names are production, so changes to them get called out

## Prompt

Every weekday at 6pm, summarize what changed in our MongoDB Atlas environment that day and keep a durable audit trail of it.

Start by calling MongoDB Atlas List Projects to get every project the credential can see. For each project, pull that day's entries with List Project Events. That operation supports date filtering, so scope it to the current day only, from midnight local time up to the run, instead of pulling the whole feed.

Group the events into meaningful buckets: cluster configuration and scaling changes, database user and role changes, network and IP access list changes, backup and restore activity, and organization or billing level changes. Skip any bucket that has nothing in it. Ignore routine automated noise such as alert open and close churn, and focus on management plane changes that a person or a key actually made.

For each bucket, write a short plain English narrative of what happened and who did it, naming the actor behind every change. Explicitly call out anything with security or availability impact, for example a new or deleted database user, an IP access list entry that widens exposure such as 0.0.0.0/0, a cluster tier change, a pause, a deletion, or a change to backup policy. Also note when a change landed outside business hours, meaning before 9am, after 6pm, or on a weekend, and when it touched a production cluster.

Create a dated page in our Compliance database in Notion using Create a Page, titled with the date, for example "Atlas change log 2026-08-07". The page holds the full categorized log: a heading for each bucket, and under it every event with its timestamp, project, cluster, actor, and event type. Since the page is created as a child of a database, ask me which Notion database to file into if the Compliance database is not already configured.

Then post the headline summary in #eng with Slack Bot Send a Message: a few lines covering how many changes there were, which ones matter, and anything flagged for security, availability, after hours, or production impact. Include a link to the Notion page so anyone can read the full log.

If nothing meaningful changed that day, say so in a single line rather than padding the report. Still file the dated Notion page with that one line so the compliance record stays continuous, and keep the Slack message to a single line too.

## How to customize

- Change the timing: run it at a different hour, or every day including weekends instead of weekdays only
- Choose which Notion database the daily pages land in, and which Slack channel gets the headline
- Adjust what counts as noteworthy: your business hours, which clusters are production, and whether quiet days still get a page

## Example output

Atlas change log for Thu 7 Aug: 9 changes across 2 projects.

Worth your attention:
• Network access: an entry allowing 0.0.0.0/0 was added to prod-payments by r.okafor at 8:42pm. Open to the whole internet and outside business hours.
• Database users: readWrite user svc-reporting created on prod-payments by automation key ci-deploy.
• Clusters: prod-payments scaled M30 to M50 by r.okafor. Brief failover during the change.

Routine: 4 backup snapshots completed as scheduled, 1 alert config edit on staging, 1 billing contact update at the org level.

Full categorized log: notion.so/Atlas-change-log-2026-08-07

## FAQ

### Does this change anything in MongoDB Atlas?

No. It only reads your activity history. The only things it writes are the summary page in Notion and the message in Slack.

### Will it work if we have more than one Atlas project?

Yes. It checks every project your Atlas login can see and organizes the report so you can tell which project each change belongs to.

### How far back does it look?

Just the current day. Each run covers only that day's activity, so you end up with one clean page per date rather than overlapping reports.

### What happens on days when nothing changed?

You get a single line saying nothing meaningful changed, instead of a padded report. The dated page is still filed so your record stays continuous.

### Do we need a paid Notion plan for this?

No. Any Notion workspace works, as long as the compliance database has been shared with the connection so pages can be added to it.

Use this prompt in General Input: https://www.generalinput.com/prompts/daily-mongodb-atlas-change-log-with-a-notion-audit-trail