Daily MongoDB Atlas change log with a Notion audit trail

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.