How to Configure Zapier Supabase Read Only Access

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up zapier supabase read only access by making a dedicated database role. You then give that role read permissions on specific tables before linking your workflow tool. Many teams skip this step and use the default project admin role instead. Sharing that main password gives an external tool full write and delete powers across your data. If a workflow has a bug, it can change or wipe out your records. How zapier supabase read only access works Every project starts with a default postgr

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 zapier supabase read only access by making a dedicated database role. You then give that role read permissions on specific tables before linking your workflow tool. Many teams skip this step and use the default project admin role instead. Sharing that main password gives an external tool full write and delete powers across your data. If a workflow has a bug, it can change or wipe out your records.

How zapier supabase read only access works

Every project starts with a default postgres role that holds admin privileges. The platform does not grant full superuser status because that allows destructive database actions. Even so, the default postgres role has extra rights for most management tasks. The password you pick when you create a project belongs to this admin role.

Platform rules say you should never give this main password to a third-party service. Instead, you should make a fresh database user for every outside tool you link. You run these setup steps in the dashboard, which executes queries as the admin role. Dashboard queries also add a small source comment to the query text.

Your new user starts with no rights to change or delete any table rows. You grant it permission to read only the specific schemas and tables your workflow needs. Each project also comes with built-in roles like anon, authenticated, service_role, and authenticator. For direct database workflows, a dedicated custom role keeps third-party permissions clean and separate.

What native read roles solve and what they miss

A dedicated read role stops accidental writes, updates, and table drops from your automation tool. If someone edits a workflow step by mistake, the database blocks any write attempt. It also lets you rotate or drop the password for one tool at any time. Your other services keep running without interruption.

Still, database roles only check who logs in and which tables they can read. Once the role has read access to a table, it can pull every column by default. That often includes sensitive fields like emails, phone numbers, card numbers, or national IDs. A static password stored in an external app also stays active until you change it.

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.

Native roles do not filter sensitive fields in flight when a query runs. If a table holds customer emails or card numbers, the workflow pulls that raw data. You have to manage extra database views if you want to hide specific columns. Teams also struggle to track which team member built or triggered a given automated query.

Why teams separate automation roles by workflow

Putting all your automated tasks on one shared database user creates a new blind spot. When a slow query locks up a table, you cannot tell which task caused it. Making a separate read role for each major integration helps you spot bad queries fast. You can also cancel a single runaway query without breaking your other background jobs.

Good role hygiene means reviewing which tables your external tools read every few months. Old workflows often keep reading sensitive tables long after a project ends. Removing table rights from unused roles shrinks your risk if an outside account gets compromised. Pairing strict database roles with field-level controls keeps customer data safe during routine automation.

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 the default postgres password for third-party workflows?

No, you should never share the default postgres password with an outside service. You should create a dedicated database user with limited read rights for each tool instead.

Does the default postgres role have superuser rights?

No, the platform does not grant superuser access because it allows destructive database operations. The default postgres role is an admin role with extra privileges for select tasks.

What happens if a read-only role tries to change data?

The database rejects any insert, update, or delete statement sent by that user. Your workflow step will fail safely without changing any records in your tables.

The query runs. The emails stay hidden.