How to Configure Make Neon Credentials

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up make neon credentials by creating a dedicated Postgres role for your workflow. You then store the database host, user, and secret key inside Make. Teams often paste the default Neon project owner string into their automation builder. That quick path gives a cloud workflow full rights to drop tables or read every row. A safer setup scopes the database role to the exact tables the workflow needs. How make neon credentials work in automation Neon runs serverless Postgres and separate

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 neon credentials by creating a dedicated Postgres role for your workflow. You then store the database host, user, and secret key inside Make.

Teams often paste the default Neon project owner string into their automation builder. That quick path gives a cloud workflow full rights to drop tables or read every row. A safer setup scopes the database role to the exact tables the workflow needs.

How make neon credentials work in automation

Neon runs serverless Postgres and separates storage from compute across branches. Each branch has its own endpoints, roles, and database objects. Make connects to these endpoints using standard Postgres modules or HTTP calls.

When you build a workflow, Make asks for the host, database name, user, and password. It saves these values as a reusable item inside your team workspace. Every time the workflow runs, Make opens a session to Neon using that stored secret.

Because Neon endpoints sit on the public network by default, strong secrets matter. You should require TLS encryption on every link between Make and Neon. You can also use Neon IP allowlists if your Make plan provides static outbound addresses.

Start by creating a fresh role inside your Neon production branch. Grant this role select, insert, or update rights on only the target tables. Never grant superuser or branch owner rights to an external workflow tool. If a workflow only reads reporting data, bind its user to a read-only compute endpoint.

What native role scoping solves and what it misses

Scoped Postgres roles stop a broken workflow from deleting tables outside its grant list. Separate credentials per workflow also help when you need to rotate a leaked password. You can update one secret without breaking every other job in your workspace.

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

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Still, native database credentials only check who logs in at the start of a session. Once the user logs in, Postgres trusts every query that fits the role grant. It cannot tell if a human changed the Make scenario to pull customer records. It also cannot block a sudden bulk update caused by a bad webhook loop.

Shared workspace secrets create another gap for security teams. Any builder with edit rights in that Make folder can use the stored link. They can attach a new module and run raw SQL queries using that same role. In the database logs, every query looks the same because they share one username.

Native roles also return raw values for every column the user can read by default. If a table holds emails, phone numbers, or card numbers, the workflow receives them all. The database does not rewrite matched fields in results before they reach the automation tool. Teams that need query-level checks and field masking must look beyond static database passwords.

Best practices for safer database workflows

Test all new Make scenarios against a non-production Neon branch first. Neon branches let you test schema changes with fake data before touching live tables. Give your test branch its own unique role and password.

Review your database roles every quarter and drop unused accounts. Check which Make scenarios still run and remove old links from inactive folders. Keep write grants narrow so automated tasks only touch the columns they must update.

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

Should Make use the default Neon owner role?

No, the default owner role can drop tables and change schemas across the database. Always create a separate Postgres role with grants limited to specific tables and actions.

How do I handle SSL when linking Make to Neon?

Enable TLS in the Make Postgres module settings so traffic stays encrypted in transit. Neon requires secure connections by default to protect data moving over public networks.

Can I use Neon branches to test Make workflows?

Yes, you can create an isolated Neon branch with test data for development scenarios. Point your test Make module to the branch host before switching to production credentials.

The query runs. The emails stay hidden.