How to Configure Make Postgres Credentials

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up make postgres credentials by creating a dedicated database role with scoped table rights. Then you store that user login and network route inside your automation tool. Teams often start by pasting an admin account into their automation workflow to move fast. That shortcut gives every automated scenario full power to change schemas or read sensitive rows. A broken module or bad input can then wipe out production tables in seconds. How to set up make postgres credentials with least pr

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 set up make postgres credentials by creating a dedicated database role with scoped table rights. Then you store that user login and network route inside your automation tool. Teams often start by pasting an admin account into their automation workflow to move fast. That shortcut gives every automated scenario full power to change schemas or read sensitive rows. A broken module or bad input can then wipe out production tables in seconds.

How to set up make postgres credentials with least privilege

A safe setup starts inside the database before you touch your automation workspace. You create a group role that holds the exact rights your workflows need. Then you create a login user for your automation tool and add it to that group. If the scenario only reads data, you grant the read privilege on specific tables or views. PostgreSQL even lets you grant read rights on specific columns of a table. This keeps secret columns out of reach while still allowing the workflow to run.

You also need to check the built-in public group role on your database server. By default, every role gets rights to log in, make temporary tables, and run functions. In older database versions, the public group could also create new objects in the public schema. Modern versions block this by default, or an admin can revoke that right manually. After locking down the role, you add the host, port, and user key to Make. You should also require encrypted transport so passwords and query results do not travel in plain text.

Why static database roles leave an operational gap

Scoped roles are a great first step, but they only check who logs in at the start. Once the automation tool opens a session, the database trusts every query that role can run. A workflow with read rights on a customer table can still pull every phone number at once. Column grants help, yet they are hard to maintain across hundreds of changing tables and views.

Static keys stored in third-party cloud tools also create a rotation burden for your engineering team. When you rotate a password, you must update every saved module before scheduled jobs fail. Because of that pain, teams leave long-lived passwords in place for months or years. Native database roles also cannot pause a risky update command and ask a human for approval. They cannot rewrite sensitive fields like emails or card numbers inside query results on the fly.

Ephemeral Credentials + End-to-End Encryption: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Scoping automation workflows by action

To keep production data safe, teams separate read workflows from write workflows at the role level. Reporting scenarios get a read-only user that can only touch clean views built for external apps. Sync scenarios that insert leads or update orders get a narrow write user for those exact tables. Separating these logins ensures a reporting bug never alters customer records.

You should also audit which team members can edit scenarios that use these saved database logins. In many workspaces, anyone who can build a workflow can reuse an existing database login. That means a staff member could build a new flow that dumps rows to an external sheet. Pairing tight database grants with strict workspace sharing rules reduces the blast radius of mistakes.

Run guardrails and masking on the Postgres connection

Role grants and firewall rules are needed setup. Setup alone cannot check single SQL statements or mask sensitive rows in a response. By design, hoop.dev is an open-source proxy that sits beside Postgres, RDS, or Aurora as a sidecar for your Postgres. Clients and agent tools keep their credentials and point their connection string at the listener.

On each query, hoop.dev guardrails refuse disallowed drops, deletes, or table reads before they run. Next, hoop.dev data masking rewrites sensitive fields in returned rows that match your rules. Furthermore, hoop.dev holds SOC 2 Type II and logs every statement and verdict per resource. Check out the project on GitHub.

Frequently asked questions

Should I use my main database admin login in Make?

No, you should never use an admin login for automated workflows. Create a dedicated login role that only has rights on the exact tables your scenario needs.

How do I limit Make to reading specific columns in PostgreSQL?

PostgreSQL lets you grant the read privilege on specific columns of a table or view. The automation user can then query those allowed columns while other columns remain blocked.

Why can my new read-only role still run database functions?

PostgreSQL grants function execution rights to the default public role on new objects. Your database admin must revoke those default rights from the public role to block function runs.

The query runs. The emails stay hidden.