How to Configure Make Neon Read Only Access
To set up make neon read only access, create a restricted Postgres role in your database. Then pair that role with a read-only compute endpoint in your Make scenario. Many teams start by pasting their default database owner string into Make. That shortcut gives every automation scenario full power to edit or drop production tables. A small bug in a scenario filter can wipe out live customer records in seconds. How to set up make neon read only access Neon splits storage from compute, which gi
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 make neon read only access, create a restricted Postgres role in your database. Then pair that role with a read-only compute endpoint in your Make scenario. Many teams start by pasting their default database owner string into Make. That shortcut gives every automation scenario full power to edit or drop production tables. A small bug in a scenario filter can wipe out live customer records in seconds.
How to set up make neon read only access
Neon splits storage from compute, which gives you two layers for read-only control. The first layer is a dedicated read-only compute endpoint in your Neon project. This endpoint points to your branch data but blocks all write calls at the compute level. Even if a workflow sends an update query, the read-only compute node rejects it right away. You can also scale this compute node on its own so heavy Make runs do not slow your main app.
The second layer is a standard Postgres role with read-only permissions inside the database. You create a new database user and grant usage on the target schema. Next, you grant select rights on the specific tables that Make needs to read. You also set default privileges so future tables in that schema stay readable when needed. When you put the read-only role and the read-only endpoint together, your Make connection string stays locked down.
Once your Neon role and endpoint are ready, you add the Postgres module inside Make. You enter the host address of the read-only compute node and the credentials for your restricted user. You also turn on encrypted transport so data stays safe while moving between Make and Neon. Before you turn the scenario on, run a single test step to check that select queries return rows and insert queries fail.
Where native database roles fall short for automation
Native roles and read-only endpoints solve the big problem of accidental writes from automation tools. Your Make scenarios can pull reports, sync leads, or check order states without risking data loss. Still, database roles only decide who can log in and which whole tables they can read. Once the role has select rights on a customer table, it can pull every column in that table by default.
Auditor Read-Only Access + Customer Support Access to Production: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
That creates a gap when tables hold private fields like emails, phone numbers, card numbers, or national IDs. A Make scenario that only needs a user status and signup date still pulls those private fields into its run history. Every person who can view the Make scenario logs can see the raw results returned by the query. Also, static database passwords stored in third-party workflow tools are hard to rotate without breaking active jobs.
Keeping sensitive columns and static keys under control
Teams often try to fix column exposure by building Postgres views for each Make scenario. Views work for one or two workflows, but they pile up fast as teams build dozens of automations. Every schema change then requires you to update a long chain of custom views and role grants. A better path is to keep roles simple and apply field rules and query checks while queries run.
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
Do I need both a Neon read-only compute endpoint and a Postgres read-only role?
Using both gives you the best safety for Make workflows. The read-only endpoint stops all writes at the compute layer. Meanwhile, the Postgres role limits which schemas and tables Make can read.
Can a read-only role hide specific columns like emails or card numbers in Make?
Standard table select grants return all columns unless you maintain separate column grants or database views. Without field-level masking in flight, sensitive values like emails, phone numbers, or card numbers still reach Make logs.
What happens in Make if a scenario tries to write to a Neon read-only endpoint?
Neon rejects the write statement right away and returns a read-only transaction error to the Make Postgres module. You can add an error handler route in Make to catch the alert and notify your team.
Related guides
In this post