How to Configure Make Neon Prevent Delete
To set up a make neon prevent delete workflow, restrict database roles and protect branches. You must remove drop and delete rights from the database user that your automation tool uses. Many teams link their automation workflows to serverless Postgres using the default owner role. This broad role lets a single bad scenario wipe out rows, tables, or whole branches. How a make neon prevent delete setup works Make runs automated tasks by sending API calls or SQL queries to your Postgres databas
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 neon prevent delete workflow, restrict database roles and protect branches. You must remove drop and delete rights from the database user that your automation tool uses. Many teams link their automation workflows to serverless Postgres using the default owner role. This broad role lets a single bad scenario wipe out rows, tables, or whole branches.
How a make neon prevent delete setup works
Make runs automated tasks by sending API calls or SQL queries to your Postgres database. Neon splits storage into branches and manages data access through standard Postgres roles. When you link these two tools, you choose either an API key or a database role. Each path carries different risks for data loss.
Control plane API keys let an automation task manage branches, endpoints, and projects. If an automated task holds a broad API key, a logic error can drop a branch. Protected branches in your database dashboard stop API calls from deleting primary branches. Turning on branch protection is your first step to stop accidental branch removal.
Inside the database, branch settings do not stop SQL queries from deleting table rows. To stop row deletion, create a custom Postgres role just for your Make scenarios. Grant this role select, insert, and update rights on the specific tables it needs. Leave out delete and truncate rights on those tables. When a scenario tries to run a delete statement, Postgres blocks the query right away.
What native roles solve and what they miss
Database roles and protected branches solve the problem of basic permission limits. They set a hard boundary on which user can log in and which commands never run. If a workflow only needs to add new leads, a restricted role works well. The database engine blocks any delete command from that user before data changes.
Still, static roles create friction when a workflow needs conditional delete rights. Some workflows must delete temporary staging rows while keeping customer records safe. Postgres grants delete rights at the table level, or requires complex row security rules. Teams often skip these hard setups and fall back to a shared admin user. They store that admin password inside the automation platform for many scenarios to share.
Static database roles also only check who logs in at the start of a session. They do not inspect the context of individual statements in flight. A valid update query with a missing filter can still overwrite every row in a table. Also, native database logs do not easily tie a bad query to one specific automation run. You see the shared database user in the log, not the exact workflow step. Also, broad select rights return raw emails, phone numbers, card numbers, and national IDs to third-party logs.
End-to-End Encryption: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
How to design safer database workflows
Start by splitting your automation tasks by the type of work they do. Never use the same database user for read tasks and write tasks. Create one read-only role for reporting workflows and another role for data entry tasks.
Use soft deletes in your tables instead of running hard delete commands. Add a status column or a timestamp column to mark rows as inactive. Your automation tool then runs an update command instead of a delete command. If a scenario makes a mistake, your team can restore the changed rows fast.
Test every new automation scenario against a separate preview branch first. Serverless Postgres makes it fast to spin up a test branch with safe data. Run your workflow against the test branch and check the query history. Move the scenario to your main branch only after you verify every query.
Check every Postgres query on the wire
Database roles and network rules decide who can open a session. They do not read what each SQL statement does after login. With hoop.dev, you run an open-source proxy, a sidecar for your Postgres. It runs beside your database and reads the Postgres wire protocol. Your apps and agents keep their login details and change only the host and port in the connection string their tool uses.
Before a query runs, hoop.dev guardrails check the statement by its effect, table, or pattern. They refuse bad deletes or drops with a real Postgres error. On the way back, hoop.dev data masking rewrites sensitive values in returned rows based on your rules. Every query and verdict goes to the audit trail. Furthermore, hoop.dev holds SOC 2 Type II, is MIT licensed, and generates evidence for HIPAA, GDPR, and PCI DSS. See the code on GitHub.
Frequently asked questions
Can branch protection stop Make from deleting table rows?
No, branch protection only stops users and API calls from deleting the entire branch. It does not block SQL delete or truncate queries running inside the database. You must restrict Postgres table permissions to stop row deletions.
How do I let a workflow archive records without delete rights?
Use a soft delete pattern by adding an active status column to your table. Grant the automation role update rights on that single column instead of delete rights. The workflow updates the status flag while the row stays safe on disk.
What happens if an automation scenario runs a blocked delete query?
Postgres rejects the query right away and returns a permission error to the automation tool. Make catches this error and stops that branch of the workflow. You can add an error handler in your scenario to alert your team.
Related guides
In this post