How to Configure Make Supabase Approval
You set up a make supabase approval flow by pausing automation jobs until a reviewer clicks approve. This setup stops your automation tool from changing database records without a human check. Teams often link automation scenarios straight to their production database to save time. They paste a single admin password into the connection settings and let workflows run. When a scenario has a bug, that broad role can wipe or alter thousands of rows. Adding a review step and scoping down database ro
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 a make supabase approval flow by pausing automation jobs until a reviewer clicks approve. This setup stops your automation tool from changing database records without a human check.
Teams often link automation scenarios straight to their production database to save time. They paste a single admin password into the connection settings and let workflows run. When a scenario has a bug, that broad role can wipe or alter thousands of rows. Adding a review step and scoping down database roles keeps your data safe from bad runs.
How the native make supabase approval workflow operates
In a standard setup, Make runs a series of steps triggered by an event or schedule. To add a review gate, you split the scenario into two separate workflows. The first workflow gathers the data and sends a message to Slack or email. That message holds a link that points to a custom webhook in the second workflow. The job stops and waits until a team lead clicks that link to approve the run. Once clicked, the second workflow wakes up and sends the change to your Supabase database.
On the database side, every Supabase project includes a default postgres role with admin rights. Supabase does not grant full superuser status because that allows destructive actions on the database. Even so, the password you set at project creation belongs to that admin postgres role. Supabase warns teams not to share this password with an outside service unless they trust it. Instead, you should create a dedicated database user for each external service you link.
Scoping database roles for external automation tools
Before you turn on your automation scenario, you need to set up a custom Postgres role. This role should only have rights to read or write the exact tables the workflow needs. If a scenario only adds new orders, the role should not have permission to delete rows. You also need to check how your workflow connects to the project.
Supabase creates a default set of built-in roles for every new project you launch. Queries that you run inside the Supabase dashboard execute under the default postgres admin role. External tools that connect direct to the database should use their own scoped login credentials. Giving Make its own restricted user limits the damage if a webhook link leaks. It also makes it easier to rotate keys for one tool without breaking other apps.
Approval Chains & Escalation + End-to-End Encryption: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
What the native setup solves and what it leaves open
Splitting a scenario and using a custom database user solves two basic problems. First, the webhook pause stops automated tasks from running blind without a human check. Second, a dedicated database user stops an external tool from owning the whole database. These steps decide which tool can log in and when a workflow can move forward.
Still, this native setup still leaves a major gap during daily operations. Database roles only check who logs in and which tables they can touch. They do not inspect what individual SQL statements or requests do while in flight. Once a role has update rights on a table, it can change one row or permitted rows (unless row-level security applies). A webhook pause in an automation tool also fails to cover engineers who connect directly. If someone runs a bad query from their laptop, the automation gate will not catch it. Standard database roles also return raw emails, phone numbers, and card numbers in query results. To fix this, teams need a way to check every command and mask sensitive fields in results.
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 I use the default postgres password in my Make connection?
No, the password set at project creation belongs to the default postgres admin role. Supabase advises creating a separate database user for every third-party service you use.
Does the default Supabase postgres role have full superuser access?
No, Supabase gives the postgres role admin privileges instead of full superuser access. This restriction blocks destructive database operations while still giving admins broad control over tables.
Can database roles hide sensitive columns like emails or card numbers in results?
Standard roles only block or allow access to whole tables or specific columns. Dynamic data masking rewrites matched fields like emails and card numbers inside query results.
Related guides
In this post