Storage

AI agents that use Supabase

UtilitySpaces gives an AI agent scoped access to Supabase through its own encrypted connection, not your password. The agent can call 3 named Supabase tools, and the one that writes waits for a person's approval unless an admin has set the connection to run without asking. Every call is written to a hash-chained audit log with its arguments and its result.

What an agent can do in Supabase

Query and insert rows in a Supabase project's Postgres tables via PostgREST. An agent calls these by name, and matching is exact.

Every tool a Supabase connection exposes, and whether it writes, which waits for approval by default
Tool	What it does	Waits for approval by default
Get schema	Get the OpenAPI description of available tables.	No — read only
Select rows	Read rows from a table; extra arguments become PostgREST filters (e.g. id=eq.5).	No — read only
Insert row	Insert one row; every argument other than table becomes a column value.	Yes — it writes

2 read tools, 1 write tool. Generated from the connector catalogue the product runs on, so it cannot list a tool that does not exist.

What teams hand an agent in Supabase

Product and data teams hand an agent the read side of their own database: discovering tables with Get schema, then answering questions with Select rows and PostgREST filters. Insert row is the single write, and it stops for approval unless an admin has set this connection to run without asking.

Answer "how many signups this week" questions in the inbox by selecting rows from the right table with a date filter.
Keep a table of events or leads current by inserting one row when a matching event arrives from another connected app (after a person approves it)
Look up a single record, such as an account by id, when someone in chat asks what the database says about it.

Before you let it write, or keep out: Select rows reads whatever the key is allowed to read, so connect a key scoped to the tables the agent needs, not the service role; nothing here updates or deletes, but Insert row on a connection set to run without asking writes without review.

What waits for a person

Reads run on their own. These do not — each one waits in Approvals for an owner or admin unless an admin has set this connection to run writes without asking, and every call toSupabase, approved, rejected or unattended, is logged.

Insert row POST

What connecting Supabase takes

Supabase uses an API key you create in Supabase and paste in once. A workspace admin sets the connection up; the fields are:

Project URL
Service Role Key

Credentials are encrypted and bound to your workspace, never read back, and every outbound call passes one guarded fetch — the connector security posture sets out exactly how, and the security page covers the platform around it.

Where Supabase fits

Give an agent Supabase work by writing a message in the inbox, or put its tools in a scheduled flow. What the run cost is on the cost breakdown.

See every application agents can connect to.

See it doing your actual work

Open a demo workspace, connect one app, and give an agent a real job. No card, no sales call.

Try the demo See pricing

We reply to every message within one business day.