How to Configure Make Postgres Approval
To set up a make postgres approval flow, pair a restricted database role with a review step. This design pauses automation scenarios until a human reviewer clears the pending database action. Many teams start by linking their automation tool straight to a main database role. That broad setup lets every automated task read or change tables without a check. If a scenario misfires, it can wipe out production rows in seconds. How a native make postgres approval workflow runs A safe automation set
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 postgres approval flow, pair a restricted database role with a review step. This design pauses automation scenarios until a human reviewer clears the pending database action. Many teams start by linking their automation tool straight to a main database role. That broad setup lets every automated task read or change tables without a check. If a scenario misfires, it can wipe out production rows in seconds.
How a native make postgres approval workflow runs
A safe automation setup splits duties between the workflow builder and the database engine. Inside the workflow tool, you add a pause step before the database module runs. The workflow sends a message to a team chat or email inbox. A reviewer checks the payload and clicks a link to resume the flow. Only then does the workflow tool open a session to the database.
On the database side, you must lock down the role used by the workflow. PostgreSQL lets admins set up group roles to manage permissions for many users. You can create a group role for automation and grant membership to the bot user. For read tasks, the SELECT privilege allows reading from specific columns of a table. It also allows reading from views, materialized views, or other table-like objects. Note that the SELECT privilege also allows COPY TO operations on those targets. By limiting SELECT to safe columns, you stop the workflow from reading secret fields.
You also need to check the default rights given to every user on the system. In PostgreSQL, the special role name PUBLIC grants privileges to every role. By default, PUBLIC gets CONNECT and TEMPORARY rights on databases. It also gets EXECUTE rights on functions and procedures out of the box. The object owner can revoke these default rights to tighten control. In PostgreSQL 15 and later, regular users cannot create objects in the public schema. Older or upgraded databases still allow this until an admin revokes CREATE from PUBLIC.
Why static roles leave a runtime gap
Combining workflow pauses with tight database roles solves the basic login problem. It defines which service account can log in and which tables it touches. Still, this native setup still leaves a major gap during live operations.
First, workflow pause steps live outside the database boundary. Anyone who edits the scenario can remove the review step and run queries right away. The database itself has no idea whether a human cleared the incoming SQL statement. Once the service account logs in, PostgreSQL trusts every command that matches its role grants.
Approval Chains & Escalation + End-to-End Encryption: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Second, static credentials sit inside the automation platform for months or years. If someone steals that saved password, they bypass the workflow review step completely. They can log in from another machine and run bulk exports using COPY TO. Native roles decide who logs in, not what individual statements do in flight.
Third, column grants are blunt tools for protecting sensitive records. If a workflow needs to read a customer table, it reads the raw text. Native database permissions cannot rewrite emails, phone numbers, card numbers, or national IDs on the fly. Teams end up building extra views or staging tables just to hide sensitive columns. That adds extra work every time a table changes.
Add query and result controls beside Postgres
Grants and pools govern who logs into PostgreSQL. Yet every query in an open session still runs with that role's full scope. In practice, hoop.dev runs beside your database as a sidecar for your Postgres. It reads plain and prepared queries on the wire with no change to your users or drivers.
When a tool or agent sends SQL, hoop.dev Postgres controls check each statement against your deny rules. An AI Analyzer you configure can also score intent or hold a risky query for human review. Matched sensitive columns in result rows are masked in memory before they reach the caller. Each query and decision is logged per listener, which generates evidence for SOC 2, HIPAA, and GDPR audits. View the binary on GitHub.
Frequently asked questions
Can a Make scenario have read access to just a few PostgreSQL columns?
Yes, PostgreSQL lets you grant the SELECT privilege on specific columns of a table. The workflow role will only be able to query the columns you list. Keep in mind that granting SELECT also allows COPY TO on those columns.
Why can a new automation role run functions without explicit grants?
PostgreSQL uses a special role called PUBLIC that applies to every role on the system. By default, PUBLIC receives EXECUTE rights on functions and procedures, plus CONNECT on databases. An object owner must revoke these default rights from PUBLIC to block the role.
Does a workflow pause step stop someone from using the database password elsewhere?
No, a pause step inside the automation builder only delays that specific scenario run. The database still relies on a static username and password stored in the tool. Moving approval checks to the database session layer ensures every query gets checked.
Related guides
In this post