How to Configure Make MongoDB Approval

Published
Length
3 min read

Luis Felipe Dias

All posts

To set up a make mongodb approval workflow, add a human review step before database actions run. You also restrict the database user to the minimum role needed for the task. Teams often build automation scenarios in Make to read or update records in MongoDB. To move fast, builders often attach one shared database user to every automated workflow. When that user holds broad write rights, a bad webhook payload can alter or delete production collections. How a native make mongodb approval workfl

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

To set up a make mongodb approval workflow, add a human review step before database actions run. You also restrict the database user to the minimum role needed for the task.

Teams often build automation scenarios in Make to read or update records in MongoDB. To move fast, builders often attach one shared database user to every automated workflow. When that user holds broad write rights, a bad webhook payload can alter or delete production collections.

How a native make mongodb approval workflow works

A native make mongodb approval workflow splits the automation scenario into two separate parts. The first scenario receives the trigger event and formats the proposed database change. Instead of writing to the database right away, it sends a message to a team chat channel or email inbox.

That message includes the key details of the proposed change and two action links. A reviewer clicks the approve link or the reject link to decide the outcome. Clicking the approve link triggers a second webhook in Make that runs the MongoDB step.

On the database side, MongoDB uses roles to control what that step can do. A role grants privileges to perform sets of actions on defined resources. A role applies to the database where you define it and works down to the collection level. MongoDB Atlas database users have different built-in roles than self-hosted users, but both use the same privilege actions.

For scenarios that only fetch data, assign the built-in read role. The read role grants read access to all non-system collections and the system.js collection in its database. It allows actions like find, listCollections, listIndexes, dbStats, collStats, and changeStream. It does not allow insert, update, remove, or dropCollection actions.

What native roles and scenario splits solve and leave open

Splitting scenarios in Make and assigning strict MongoDB roles reduces accidental damage from automated tasks. A read-only scenario cannot drop a collection if its database user only holds the read role. High-risk updates wait for a human to click an approval link before the scenario continues.

Still, scenarios that modify records need the built-in readWrite role or custom write privileges. The readWrite role includes everything in the read role plus the power to change data. Its actions include insert, update, remove, createCollection, createIndex, dropIndex, and dropCollection.

Approval Chains & Escalation + MongoDB Authentication & Authorization: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Once you store those credentials in Make, any scenario using that connection shares those broad rights. A webhook approval step in Make also relies on the scenario builder to wire every branch properly. If a builder skips the review step in a new scenario, the database cannot tell the difference.

MongoDB roles check who logs in and which collection actions they can run. They do not pause individual queries in flight to ask a human for sign-off. They also do not mask sensitive fields like emails, phone numbers, card numbers, or national IDs in query results.

How to tighten database roles for automated workflows

Start by separating read scenarios from write scenarios across all of your automation workspaces. Create one database user with the read role for reporting, syncing, and lookup tasks. Create a second user scoped to specific collections for workflows that must insert or update documents.

Avoid using the standard readWrite role when an automation only needs to insert new records. Build a custom role that grants only the insert or update action on the target collection. Remove actions like dropCollection, dropIndex, and remove so a faulty loop cannot wipe out data.

Review your active Make connections each month to check which scenarios use write credentials. Rotate database keys on a regular schedule and remove unused accounts from your cluster. Keep human review steps in place for any workflow that updates billing, user state, or account records.

Inspect MongoDB wire traffic in flight

Built-in MongoDB roles govern collection access at setup time. They cannot score command risk per call or mask sensitive document values on the fly. By design, hoop.dev is an open-source proxy that sits next to MongoDB as a sidecar for your MongoDB. It reads every command from mongosh, drivers, or agent tools.

First, hoop.dev guardrails block bad deletes, drops, and write pipelines. Next, hoop.dev data masking rewrites sensitive values in returned documents based on your rules and logs each decision. Explore the repo on GitHub.

Frequently asked questions

Can MongoDB require human approval before a query runs?

No, MongoDB checks role privileges at login and command execution, not through interactive prompts. Once a user has permission for an action like update or remove, the database runs it right away.

What is the difference between the MongoDB read and readWrite roles?

The read role allows actions like find and listCollections on non-system collections without allowing data changes. The readWrite role adds write actions including insert, update, remove, createIndex, and dropCollection.

How can I stop a Make scenario from dropping a MongoDB collection?

Do not give the automation user the full readWrite role on the database. Instead, create a custom role that grants only find, insert, and update actions on the exact collection needed.

Short role checks help teams work fast. Simple rules make each review clear. Good logs keep every team safe. Scoped keys stop bad changes early.

The query runs. The emails stay hidden.