How to Configure Make SQL Server Approval
You can set up a make sql server approval flow by pausing automation runs until a reviewer confirms the step. The scenario holds the database task and waits for a human click before it sends any SQL query. Teams often link Make to their database using one shared login. That account usually holds broad write roles across every table. If a scenario has a bug, it can change or delete critical rows right away. Adding an approval step helps teams check risky updates before they hit production data.
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.
You can set up a make sql server approval flow by pausing automation runs until a reviewer confirms the step. The scenario holds the database task and waits for a human click before it sends any SQL query. Teams often link Make to their database using one shared login. That account usually holds broad write roles across every table. If a scenario has a bug, it can change or delete critical rows right away. Adding an approval step helps teams check risky updates before they hit production data.
How a native make sql server approval setup works
To build this flow, you first set up a dedicated account in your database. In SQL Server, a database user represents the identity of a login when it connects. If the tool needs many databases on one instance, admins create a login in the master database. If the tool only needs one database, admins can use a contained database user with a password. The admin must enable contained databases on the server and the database first. Microsoft provides thirteen types of database users for different needs.
Next, you assign permissions to that user. SQL Server offers fixed database roles with set permissions that you cannot change. Members of the datareader role can read all data from all user tables and views. Members of the datawriter role can add, delete, or change data in all user tables. Some teams use the owner role, which can run all maintenance tasks and even drop the database. In Make, you break your scenario into two parts. The first part sends a message to a reviewer with a link. When the reviewer clicks the link, the second part wakes up and runs the query.
What native roles and workflow steps leave open
This two-part automation setup solves basic scheduling problems. It stops a webhook or timer from firing database changes without a human check. Meanwhile, SQL Server roles control who can log in and which broad actions they can take. For example, a deny datawriter role stops a user from changing any table data. A deny datareader role blocks a user from reading any user tables or views.
Still, static database roles and workflow pauses leave a major gap open. Fixed roles apply to the whole database, not to single queries in flight. Once Make logs in as a datawriter, it can modify or delete every row in every user table by default. If the approval message in Make does not show the exact SQL text, the reviewer approves blind. Also, the stored database password sits inside the automation tool all day. Anyone who edits the scenario can use that same connection to run other queries without approval.
Approval Chains & Escalation + Kubernetes API Server Access: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Why query-level checks matter for automation
Automation tools run fast and repeat the same action thousands of times. A small mistake in a filter or variable can wipe out customer records in seconds. Relying only on workflow design means every builder must remember to add the pause step. If one builder forgets that step, the database role still lets the query run.
Real safety requires checking the actual SQL command right when the tool sends it. Teams also need a way to protect sensitive fields returned by read queries. For example, masking rewrites matched fields like emails, phone numbers, card numbers, or national IDs in results. This keeps raw personal data out of automation logs and third-party apps.
Govern SQL Server queries and responses in flight
Table grants decide which SQL Server objects a caller may touch. They do not check query intent or rewrite sensitive values in results across every client and agent. By design, hoop.dev is an open-source proxy that sits next to SQL Server as a sidecar for your SQL Server. It inspects TDS batches and parameterized queries in real time.
With hoop.dev guardrails and hoop.dev data masking, banned statements are refused with your message. Matched sensitive fields in supported result columns are masked in memory, and each decision is logged per listener. Check out the code on GitHub.
Frequently asked questions
Can we restrict the Make database user to read-only tasks?
Yes, you can add the user to the fixed datareader role and the deny datawriter role. This lets the scenario read all user tables and views while blocking any data changes.
Why is the database owner role risky for Make scenarios?
Members of the owner role can do all maintenance tasks and can even drop the whole database. If a scenario fails or gets misused, that account has no safety limits inside the database.
Does a contained database user stop bad queries from Make?
No, a contained user only limits the account to a specific database without a master login. Once inside that database, its role still decides whether it can change or delete table rows.
Related guides
In this post